Hi Karl,
There must be an explanation that neither of us know of (to date).
Sent you a screenshot via Messenger.
Could it be the fast search index was already created somewhere else?
David
Sent from [Proton Mail](https://proton.me/mail/home) for iOS
On Tue, Jul 1, 2025 at 17:00, Karl Kleinpas
David Haslam wrote:
> installed Persian Bible module FarFLB from the Xiphos repo
toPocketSword- complete with the associated fast search index, and it
all worked OK.
That's a neat trick, because there is no fast search index for FarFLB in
the repo.
I don't know what you did, but Xiphos repo
Thanks Karl,
After a refresh, I successfully installed Persian Bible module FarFLB from the
Xiphos repo toPocketSword- complete with the associated fast search index, and
it all worked OK.
NB. In general, for modules installed from the CrossWire & eBible.org repos,
the associated search indice
Thanks for all the work you all are putting into this, looking forward to
updating!
Sent from Proton Mail Android
Original Message
On 2025-03-17 8:56 a.m., Karl Kleinpaste wrote:
> A fatal module manager bug was found for 1st-time users.
> 4.3.0 release is retracted, 4.3.1 is
Installed! 😎
Best regards,
David
Sent with [Proton Mail](https://pr.tn/ref/SWXT9A5YZ67G) secure email.
On Monday, March 17th, 2025 at 12:56 PM, Karl Kleinpaste
wrote:
> A fatal module manager bug was found for 1st-time users.
> 4.3.0 release is retracted, 4.3.1 is already in place.__
Thanks Karl & team,
Successfully installed Xiphos (x64) in my Windows 11 laptop.
Confirmed that installing a module to replace an earlier module no longer
crashes Xiphos.
Bravo!!! 😎
Best regards,
David
Sent with [Proton Mail](https://pr.tn/ref/SWXT9A5YZ67G) secure email.
On Sunday, March 16
Hurray! Glad to know it worked out.
--Greg
On Thu, Jul 29, 2021 at 3:53 AM Troy A. Griffitts
wrote:
> This morning I received my bright and shiny new SWORD and Xiphos updates
> from the F34 repos. Thank you!
> On 7/19/21 5:50 PM, Greg Hellings wrote:
>
> Thanks!
>
> I've issued the rebuild com
This morning I received my bright and shiny new SWORD and Xiphos updates
from the F34 repos. Thank you!
On 7/19/21 5:50 PM, Greg Hellings wrote:
> Thanks!
>
> I've issued the rebuild commands for both Xiphos and BibleTime in
> Fedora and they've completed in F34. They should make their way into
>
Thank you so much, Greg! I appreciate your maintenance of our fedora
packages, among other things! I hope normal life isn't too rude after
an amazing honeymoon holiday!
Troy
On 7/19/21 5:50 PM, Greg Hellings wrote:
> Thanks!
>
> I've issued the rebuild commands for both Xiphos and BibleTime in
Thanks!
I've issued the rebuild commands for both Xiphos and BibleTime in Fedora
and they've completed in F34. They should make their way into the
updates-testing repositories in the next 24ish hours. After that they'll
promote to the updates repo about 7 days later automatically (It can be
faster
Congratulations and enjoy your honeymoon!
On July 14, 2021 7:13:19 PM GMT+02:00, Greg Hellings
wrote:
>Yes, this is captured in a Bugzilla that was automatically filed last
>week
>by Fedora automation. I goofed up when I packaged the Sword 1.9.0RCs
>during
>the Fedora 34 beta cycle (I misnamed t
Yes, this is captured in a Bugzilla that was automatically filed last week
by Fedora automation. I goofed up when I packaged the Sword 1.9.0RCs during
the Fedora 34 beta cycle (I misnamed the RPM package so dnf sorted the RC
as higher version than 1.9.0). I finally fixed that about a month ago, but
On 2/12/21 5:09 PM, Don Elbourne wrote:
> Forgive my ignorance, but what is the difference between Xiphos and
> BibleTime?
They represent different workflows around how one reads/studies the
Bible. Neither is necessarily better than the other, but long ago I
tried them both and found that Xiphos
On 5/10/20 11:27 AM, Karl Kleinpaste wrote:
> DNS entries have been mangled, so inaccessible.
Now fixed.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your
On 5/10/20 10:41 AM, Tobias Klein wrote:
> Xiphos repository seems to be down
Not down. DNS entries have been mangled, so inaccessible. I'll contact
Simon.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo
On 5/7/20 4:23 PM, Caleb Maclennan wrote:
> On Thu, May 7, 2020 at 11:12 PM Israel Dahl wrote:
>> Do you maintain the AUR build scripts for Arch?
> I maintain the AUR builds for xiphos (and xiphos-git). 4.2.1 was
> released there already.
>
Excellent! Thanks, I will try later on Manjaro!
>> And a
On Thu, May 7, 2020 at 11:12 PM Israel Dahl wrote:
> Do you maintain the AUR build scripts for Arch?
I maintain the AUR builds for xiphos (and xiphos-git). 4.2.1 was
released there already.
> And also do you think this will be able to get into Debian?
I can't really speak to Debian. I think for
Do you maintain the AUR build scripts for Arch?
And also do you think this will be able to get into Debian?
Thanks for your work!
On 5/7/20 10:24 AM, Karl Kleinpaste wrote:
> https://github.com/crosswire/xiphos/releases/tag/4.2.1
>
> After a long dry spell, Xiphos is back with a new release. This
Thanks Karl.
Well done everyone involved.
Is there any guidance for Windows users who had previously installed the x86
edition of version 4.1.0 but would like to install the x64 edition as the
update to version 4.2.1 ?
Will running the install work smoothly in this situation or should I first
Hi David,
He's not speaking about the xiphos repo, but xiphos in the ubuntu
official repo. Ubuntu 20.04 used the debian testing and xiphos was
removed from testing because of an obsolete dependancy.
Le 04/05/2020 à 20:59, David Haslam a écrit :
> If it were down momentarily, it’s already back up.
If it were down momentarily, it’s already back up.
David
Sent from ProtonMail Mobile
On Mon, May 4, 2020 at 19:57, David Haslam wrote:
> Why do you think it were removed rather than just being temporarily down ?
>
> It was OK yesterday.
>
> I expect Karl will have it back up in a jiffy.
>
> As
Why do you think it were removed rather than just being temporarily down ?
It was OK yesterday.
I expect Karl will have it back up in a jiffy.
Aside: Some VPN services don’t allow FTP access to the Xiphos org repo, but
that’s not today’s issue.
AFAIK, you were asking only about the repo.
Davi
Le 04/05/2020 à 20:50, Israel Dahl a écrit :
> Hi,
>
> Why was Xiphos removed from the repositories?
Because we released to late... For now you can use my ppa for focal:
https://launchpad.net/~lafricain79/+archive/ubuntu/lafricaintest
Keep in touch with us, they probably offer the new release in
Le 05/11/2019 à 11:01, Karl Kleinpaste a écrit :
> On 11/5/19 10:31 AM, Cyrille wrote:
>> #6 0x71f9fca2 in __strcpy_chk (dest=0x57492190 "",
>> src=0x566bed50 "ထွက်မြောက်ရာကျမ်း 1:1", destlen=50)
>> at strcpy_chk.c:30
> Bug found. A fix will happen for next release. That won'
On 11/5/19 10:31 AM, Cyrille wrote:
#6 0x71f9fca2 in __strcpy_chk (dest=0x57492190 "",
src=0x566bed50 "ထွက်မြောက်ရာကျမ်း 1:1", destlen=50)
at strcpy_chk.c:30
Bug found. A fix will happen for next release. That won't be today or
next week, but ... I'm thinking Christmas or th
Le 05/11/2019 à 10:22, Karl Kleinpaste a écrit :
> On 11/5/19 10:20 AM, Cyrille wrote:
>> But I don't know what means gdb. Let me know how to do.
> http://ftp.xiphos.org/sword/debugging/backtrace
Thread 1 "xiphos" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/
On 11/5/19 10:20 AM, Cyrille wrote:
But I don't know what means gdb. Let me know how to do.
http://ftp.xiphos.org/sword/debugging/backtrace
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
In
Le 05/11/2019 à 10:18, Karl Kleinpaste a écrit :
> On 11/5/19 9:09 AM, Cyrille wrote:
>> |*** buffer overflow detected ***: xiphos terminated|
> It would help if you could run it under gdb to get a backtrace for
> what function/line is the choke point.
I'm ready to do everything! But I don't know
On 11/5/19 9:09 AM, Cyrille wrote:
|*** buffer overflow detected ***: xiphos terminated|
It would help if you could run it under gdb to get a backtrace for what
function/line is the choke point.
___
sword-devel mailing list: sword-devel@crosswire.org
h
Thank you for the clarification! Now if we could just get a more recent Sword
engine into distribution on Ubuntu, that would be nice...
On 06/13/2018 12:56 PM, Karl Kleinpaste wrote:
> On 06/13/2018 06:49 PM, Karl Kleinpaste wrote:
>> Xiphos' MinimumVersion support was added Aug 2017, released in
Thank you, Michael. Sorry I didn't act on your prior email. I get way too much
email to properly deal with it all. Anyway, since front end developers are so
slow to upgrade their sword engine use, I downgraded my module generation to
specify a minimum sword version of 1.7.0. The downside of this
On 06/13/2018 06:49 PM, Karl Kleinpaste wrote:
> Xiphos' MinimumVersion support was added Aug 2017, released in 4.0.7,
> Sep 2017.
BTW, this explains the variability of success from testing:
Xiphos
4.1.0
1.8.1
Windows 10
PASS
Xiphos
4.0.7
1.7.3
On 06/13/2018 06:38 PM, Michael H wrote:
> Xiphos and Bibletime are properly testing the module minimum
> requirements against the sword engine
Xiphos' MinimumVersion support was added Aug 2017, released in 4.0.7,
Sep 2017.
___
sword-devel mailing list: s
Kahunapule,
I sent you an email about this about 9 months ago:
The issue might be that all of the modules on ebible.org have a minimum
requirement for sword 1.7.4 in place, regardless of actual module content
vs. sword engine capabilities. (I did not validate ALL, but I have tested
~20 or so modu
I will add this case:
Bibletime
2.11.1
1.8.1
Ubuntu 18.04
PASS
Bibletime
2.11.1
1.7.3
Ubuntu 18.04
Fails
The pattern seems to be Sword 1.81 pass, Sword 1.7.3 fail.
Based on how BibleTim
Thank you, Pierre.
The two installmgr commands you suggested worked on Ubuntu 18.04. Xiphos still
failed.
On 06/13/2018 08:47 AM, pierre amadio wrote:
> Hi there !
>
> I do not have a Ubuntu 18.04 ready to try out, but you should be able to
> check wether the problem is within the sword library
Hi there !
I do not have a Ubuntu 18.04 ready to try out, but you should be able to
check wether the problem is within the sword library itself by trying to
perform the same task with installmgr.
installmgr -r eBible.org
installmgr -ri eBible.org fraLSG1910eb
If this did not work, double check i
I'm looking for a pattern in what works and what doesn't. Here is the test:
install a Bible unique to eBible.org.
Front end
version
Sword version
OS
Result
Xiphos
4.1.0
1.8.1
Windows 10
PASS
Xiphos
4.0.7
1.7.3
Seems I can't get either http nor ftp eBible repository on Xiphos 4.07
on Ubuntu Bionic.
Robert.
On 13/06/18 15:36, Michael Johnson wrote:
Yes, I refreshed the standard list of sources and manually refreshed
eBible.org. I got a blank list.
On 06/12/2018 05:14 PM, Greg Hellings wrote:
Did y
It's still working for me with Xiphos 4.1.0 for Windows.
David
Sent from ProtonMail Mobile
On Wed, Jun 13, 2018 at 04:36, Michael Johnson wrote:
> Yes, I refreshed the standard list of sources and manually refreshed
> eBible.org. I got a blank list. On 06/12/2018 05:14 PM, Greg Hellings wrote
Yes, I refreshed the standard list of sources and manually refreshed
eBible.org. I got a blank list.
On 06/12/2018 05:14 PM, Greg Hellings wrote:
> Did you go through the normal path of refreshing the standard list of sources?
>
> --Greg
>
> On Tue, Jun 12, 2018 at 10:03 PM Kahunapule Michael Joh
On 06/12/2018 11:01 PM, Kahunapule Michael Johnson wrote:
> Is there anything I can do about it, or is this something that needs to be
> fixed in Xiphos?
I just refreshed eBible in Xiphos without incident. It appears in 2
configurations in my Installmgr.conf; both work for me:
FTPSource=eBible.o
Did you go through the normal path of refreshing the standard list of
sources?
--Greg
On Tue, Jun 12, 2018 at 10:03 PM Kahunapule Michael Johnson <
kahunap...@ebible.org> wrote:
> I just set up a new Linux (Ubuntu Bionic Beaver) system for someone,
> including an install of Xiphos. When trying t
On 04/18/2018 10:34 PM, Fred Smith wrote:
> #829, below, is not windows only. it occurs on LInux, too, In, at least,
> the epel build for RHEL/Centos.
> So I did a local build and the problem remains.
Not if you built out of the 4.1.0 tarball, or have updated with git
pull. The relevant commits are
#829, below, is not windows only. it occurs on LInux, too, In, at least,
the epel build for RHEL/Centos.
So I did a local build and the problem remains.
On Wed, Apr 18, 2018 at 09:55:49PM -0400, Karl Kleinpaste wrote:
>A bit late from original plan, but here it is.
>4.1.x is expected to be
Not long afterwards, I added an issue in the Xiphos github repo.
https://github.com/crosswire/xiphos/issues/826
David
--
Sent from: http://sword-dev.350566.n4.nabble.com/
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.o
Y'know, there are mailing lists for Xiphos. They're even hosted here on
crosswire.org these days.
On 09/27/2017 12:32 PM, Fred Smith wrote:
> Is there anything critical in that list of errors?
Nope. Tell it to the GTK folks who can't manufacture sensible,
self-consistent GTK themes; those aren't
On Mon, Sep 25, 2017 at 09:24:26PM -0500, Greg Hellings wrote:
>It's been a minute (4.0.4) since I shipped an EPEL build. But I just
>put one together for EPEL7. Please, please, please test it once it hits
>the updates-testing repo at the next compose (ideally that should be
>tomorr
Clarification - further evidence.
I was able to install a new module from eBible.org
Xiphos closed ONLY when I selected a module under Updates and attempted to
install that.
After the crash, the Xiphos MM no longer listed the same module under
Updates even after a further refresh.
Moreover, ther
Just tried installing a module from the eBible.org repository.
Repository refresh worked fine.
Xiphos 4.0.7 (Win32) just closed (crashed?) during attempt to install
module.
No progress bar movements prior to the crash.
The behaviour is repeatable.
Installing one from CrossWire Main worked OK.
Is
FYI "Unit 193" already got it into Debian unstable.
https://packages.debian.org/sid/xiphos
The Ubuntu ppa https://launchpad.net/~pkgcrosswire/+archive/ubuntu/ppa
is way out of date, so if anyone wants to help get the package there
they would be welcome. And someone may get it into Debian backports
On Mon, Sep 25, 2017 at 09:24:26PM -0500, Greg Hellings wrote:
>It's been a minute (4.0.4) since I shipped an EPEL build. But I just
>put one together for EPEL7. Please, please, please test it once it hits
>the updates-testing repo at the next compose (ideally that should be
>tomorr
It's been a minute (4.0.4) since I shipped an EPEL build. But I just put
one together for EPEL7. Please, please, please test it once it hits the
updates-testing repo at the next compose (ideally that should be tomorrow,
but it could be anytime in the next few days) and let me know if I've
horribly
On Mon, Sep 25, 2017 at 07:03:26PM -0500, Greg Hellings wrote:
>Builds for Fedora Rawhide, Fedora 27 (currently in alpha) and Fedora 26
>are currently underway. They'll filter into their respective repos over
>the next 0 to 7 days, depending on the QE cycle for your particular
>rele
Builds for Fedora Rawhide, Fedora 27 (currently in alpha) and Fedora 26 are
currently underway. They'll filter into their respective repos over the
next 0 to 7 days, depending on the QE cycle for your particular release.
--Greg
On Mon, Sep 25, 2017 at 8:20 AM, David Haslam wrote:
> Installed th
Installed the x64 edition in Windows 7 this morning. Not had time to use it
yet.
Updated the Xiphos page in the SWORD developers' wiki.
David
--
Sent from: http://sword-dev.350566.n4.nabble.com/
___
sword-devel mailing list: sword-devel@crosswire.or
On 09/08/2017 07:13 AM, Greg Hellings wrote:
> You could host it on Amazon S3 as HTTP/HTTPS only for pennies a month
Or I could recycle another old box for $0.
The now-failed hardware lasted 12 years.
___
sword-devel mailing list: sword-devel@crosswire.or
You could host it on Amazon S3 as HTTP/HTTPS only for pennies a month
On Sep 8, 2017 05:58, "Karl Kleinpaste" wrote:
> FYI the host personifying ftp.xiphos.org failed last night.
> I should have a solution in place this evening.
>
> ___
> sword-devel m
On 08/11/2017 09:43 AM, David Haslam wrote:
> Are there any special instructions for installing the x64 edition, for a
> Windows user that had previously installed the x32 edition?
It's some sort of stupid glitch in the NSIS file that I've never figured
out. It insists on going to the wrong direc
Thanks, Karl.
In the Windows edition, for Xiphos 4.0.6 Help About, the copyright date
range still ends with 2016. You may wish to fix this.
(It was still like this in 4.0.5 - though I forgot to report it when I first
noticed.)
btw. I might help users if the Help About also indicated whether the
BTW... I had a couple reports of Xiphos under Win10 crashing in the
previous release, both 32- and 64-bit builds. I am unable to reproduce
this. I have Win10 on my desk at work and on my woman's laptop, and
Win7 in a VBox VM, and have no trouble with Xiphos on any of these.
If you see such a fai
It's indirect, in that the Xiphos help options include a link to the Manual,
and the Manual has links to the gnomesword-users list.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Xiphos-4-0-5-tp4657084p4657097.html
Sent from the SWORD Dev mailing list archive at N
On 04/24/2017 05:26 AM, David Haslam wrote:
> Is that still being used since you moved to GitHub?
I can't find gnomesword-users anywhere in my Xiphos tree. Tell me where
you see it.
> The Manual is seven years old, and there's not been any update forthcoming
> from the "Xiphos Team" since
No,
This is just a friendly observation, not a complaint.
A "first-time user" might be confused by the fact that the *Xiphos Help* is
so old that it still points users to get online help from
gnomesword-us...@lists.sourceforge.net
Is that still being used since you moved to GitHub?
The Manual is s
Hi Karl,
The splash screen still sports "Copyright © 2000-2016 Xiphos Development
Team"
Suggest update it to read "Copyright © 2000-2017 Xiphos Development Team"
Blessings,
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Xiphos-4-0-5-tp4657084p4657090.html
Sent
Hi Karl,
New release recorded in
https://crosswire.org/wiki/Frontends:Xiphos#Release_history
What's the reason to /recommend/ the *x32 edition* for users who (like me)
have Windows 7 x64 ?
Have you had any useful feedback from users of the x64 edition?
Does not the recommendation itself foresta
Versions of Xiphos have been built into the standard repositories for
Rawhide, Fedora 26 (current alpha - will be available in 3 days in
updates), and Fedora 25 (current stable - will be available in 7 days in
updates).
--Greg
On Sun, Apr 23, 2017 at 8:32 PM, Karl Kleinpaste
wrote:
> An act of
On 2016-01-25, 15:22 GMT, Karl Kleinpaste wrote:
> The code base will be auto-imported from SF; at the moment,
> the repo at https://github.com/crosswire/xiphos is empty and
> will stay that way until I collect a bunch of new GitHub names
> so that the import can "credit" past commits properly.
I hope all goes well for the move, Karl.
I'm sure it's the right thing to do, even if as one aging volunteer, I'm not
yet up to speed.
At least I do already have a registered account on GitHub.
https://github.com/DavidHaslam
Nothing there to see yet - that would interest coders.
btw. The profile
Yeah, tell it to Comcast, who have been ditching service in this area on
and off for 3 days. I hope it'll be back again in a couple hours.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instr
On 2015-12-16, 20:22 GMT, Troy A. Griffitts wrote:
> Hi guys. How were the modules installed? Where are they installed?
> Are the data files readable by the user running these commands?
1) Checked for all material installed in $HOME and removed it
(including ~/.sword).
2) $ installmgr -init
Hi guys. How were the modules installed? Where are they installed?
Are the data files readable by the user running these commands?
On 12/16/2015 11:58 AM, Matěj Cepl wrote:
> On 2015-12-10, 13:59 GMT, Mark Trompell wrote:
>> 2015-12-10 10:10 GMT+01:00 Matěj Cepl :
>>> On 2015-10-29, 11:58 GMT, K
On 2015-12-10, 13:59 GMT, Mark Trompell wrote:
> 2015-12-10 10:10 GMT+01:00 Matěj Cepl :
>> On 2015-10-29, 11:58 GMT, Karl Kleinpaste wrote:
>>> On 10/19/2015 06:36 AM, Matěj Cepl wrote:
could anybody suggest why xiphos shows me just blank pages
>>> I just came back to this after watching your
On 2015-12-10, 13:59 GMT, Mark Trompell wrote:
> Did you try with a fresh ~/.xiphos?
Now, I did. No change.
Matěj
--
https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz
GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC
Two things fill the heart with renewed and increasing aw
2015-12-10 10:10 GMT+01:00 Matěj Cepl :
> On 2015-10-29, 11:58 GMT, Karl Kleinpaste wrote:
>> On 10/19/2015 06:36 AM, Matěj Cepl wrote:
>>> could anybody suggest why xiphos shows me just blank pages
>> I just came back to this after watching your video when you first sent
>> this last week. I have
On 2015-10-29, 11:58 GMT, Karl Kleinpaste wrote:
> On 10/19/2015 06:36 AM, Matěj Cepl wrote:
>> could anybody suggest why xiphos shows me just blank pages
> I just came back to this after watching your video when you first sent
> this last week. I have no explanation, but do you get the same behav
On 10/19/2015 06:36 AM, Matěj Cepl wrote:
> could anybody suggest why xiphos shows me just blank pages
I just came back to this after watching your video when you first sent
this last week. I have no explanation, but do you get the same behavior
out of BT, for example? My only guess is some kind
It works from this side - thanks!
>
> ftp.xiphos.org's DNS has been updated, so the repo is visible again. And
> it is busy.
>
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to
On 09/23/2015 05:23 AM, Karl Kleinpaste wrote:
> a request to replace the old A RR with a CNAME RR
ftp.xiphos.org's DNS has been updated, so the repo is visible again. And
it is busy.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.cros
Thanks for the fix!
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
The remote VPN endpoint that has provided my home server's (as
ftp.xiphos.org's) external visibility for roughly 2 decades completely
failed last weekend. It was finally determined yesterday that that node
will not come back. So I worked out the necessary dynamic DNS and other
matters needed so t
Thanks Karl,
Installed successfully in my Win7 x64 PC.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Xiphos-4-0-4-tp4655136p4655138.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
sword-devel mail
I found the problem with anonymous ftp
with user name ftp being randomly disabled. It is because Plesk
thinks it is smarter than me, and undoes my configuration changes
whenever it regenerates configuration files from its database, but
it doesn't give me a way to
On 2015-08-17, 21:41 GMT, Karl Kleinpaste wrote:
> On 08/17/2015 04:44 PM, Matěj Cepl wrote:
>> I still don’t know what's the advantage of lying about the API version.
> I suppose it's a small example of a much larger problem. If GTK3 is
> updated from 3.14.15 to 3.14.16, we shouldn't induce a reb
On 2015-08-17, 21:17 GMT, Greg Hellings wrote:
> The point is that, if we build against 1.1.2 (the way we used to build
> against 1.7.1 of SWORD, etc) then we are forced to execute a rebuild
> of the Xiphos and all other downstream packages just because the
> filename changes to 1.1.3 later on. Eve
On 08/17/2015 04:44 PM, Matěj Cepl wrote:
> I still don’t know what's the advantage of lying about the API version.
I suppose it's a small example of a much larger problem. If GTK3 is
updated from 3.14.15 to 3.14.16, we shouldn't induce a rebuild of all
GTK3 applications. Current /usr/lib64/libgt
The point is that, if we build against 1.1.2 (the way we used to build
against 1.7.1 of SWORD, etc) then we are forced to execute a rebuild
of the Xiphos and all other downstream packages just because the
filename changes to 1.1.3 later on. Even though 1.1.2 and 1.1.3 are
API/ABI compatible. By exp
On 2015-08-17, 19:10 GMT, Karl Kleinpaste wrote:
> I pulled down the official (i.e. Greg's) BibleSync packages from Fedora
> repos to look inside them. His packages contain .so.1.1, not
> .so.1.1.2. Perhaps Greg did the soversion thing? But in the name of
> consistency, then, a Xiphos built agai
On 2015-08-17, 18:18 GMT, Greg Hellings wrote:
> Are you certain that you're calling up the xiphos that came from my
> packages? My biblesync build script never generates a
> biblesync.so.1.1.2 at all, so there should be no way for the Xiphos
> package to be created while referencing it. If the bib
I pulled down the official (i.e. Greg's) BibleSync packages from Fedora
repos to look inside them. His packages contain .so.1.1, not
.so.1.1.2. Perhaps Greg did the soversion thing? But in the name of
consistency, then, a Xiphos built against that BibleSync package should
link fine using just .s
Matej,
Are you certain that you're calling up the xiphos that came from my
packages? My biblesync build script never generates a
biblesync.so.1.1.2 at all, so there should be no way for the Xiphos
package to be created while referencing it. If the biblesync spec file
was generating a library file
On 2015-08-17, 13:00 GMT, Karl Kleinpaste wrote:
> I can't offer any guess, being not involved in Redhat repo management.
> My builds use a spec that started as mostly Greg's. Your version lacks
> Greg's -fPIC additions from several months ago (F22 got uptight about
> security in some new, weird s
On 08/17/2015 12:42 AM, Matěj Cepl wrote:
> I didn’t build it, it was downloaded from the official EPEL repo.
Sorry, my mistake, I thought you were experimenting with the build
process for it as well.
> Why in the world, we define that __soversion macro? I have never
> in my life with SPEC files (
On 2015-08-16, 23:07 GMT, Karl Kleinpaste wrote:
> On 08/16/2015 05:55 PM, Matěj Cepl wrote:
>> Shouldn’t that library be /usr/lib64/libbiblesync.so.1.1.2 ?
> Absolutely. Did you update biblesync.spec appropriately when it was
> built, and did you build it from the right .tar.gz in the first place
Thanks Karl.
All works now.
Karl Kleinpaste wrote:
On 08/16/2015 07:52 PM, Brian Schroeder wrote:
Is their something wrong with the eBible site at the moment?
If you set it upin mod.mgr for FTP usage, the problem is that anon FTP
has been disabled at this time. I don't know why.
$ ftp ftp.
On 08/16/2015 07:52 PM, Brian Schroeder wrote:
> Is their something wrong with the eBible site at the moment?
If you set it upin mod.mgr for FTP usage, the problem is that anon FTP
has been disabled at this time. I don't know why.
$ ftp ftp.ebible.org
Connected to ftp.ebible.org (74.208.71.128).
I have just built Xiphos 4.0.3 rpms on Mageia 5, and installed the gtk3
version. It all seems to work normally.
However I am not able to see any modules in the eBible repository. I
added it in in the module manager and refreshed. The refresh seemed to
run too quickly, and then no modules sho
On 08/16/2015 05:55 PM, Matěj Cepl wrote:
> Shouldn’t that library be /usr/lib64/libbiblesync.so.1.1.2 ?
Absolutely. Did you update biblesync.spec appropriately when it was
built, and did you build it from the right .tar.gz in the first place?
___
sword-
On 2015-08-16, 17:56 GMT, Karl Kleinpaste wrote:
>> xiphos: error while loading shared libraries: libbiblesync.so.1.1.2:
> cannot open shared object file: No such file or directory
>
> How can you have installed biblesync and biblesync-devel without getting
> their files in place?
matej@mitmanek:
On 08/16/2015 01:43 PM, Matěj Cepl wrote:
> What's wrong with me? Shouldn't
> distro-sync be enough? It seems to me that some package is
> missing proper Requires.
Um...
> xiphos: error while loading shared libraries: libbiblesync.so.1.1.2:
cannot open shared object file: No such file or directo
1 - 100 of 266 matches
Mail list logo