Now it should just be a matter of waiting for everything to build.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/935574
Title:
ABI incompatability in libsword8 (xiphos segfaults)
To manage notifica
This bug was fixed in the package xiphos - 3.1.5+dfsg-1
---
xiphos (3.1.5+dfsg-1) unstable; urgency=low
[ Dmitrijs Ledkovs ]
* New upstream release.
* Build using webkit backend
* Contains unpacked source for waf binary (Closes: #654511)
* Update debian/copyright to lates
** Branch linked: lp:ubuntu/biblememorizer
** Branch linked: lp:ubuntu/bibletime
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/935574
Title:
ABI incompatability in libsword8 (xiphos segfaults)
To
This bug was fixed in the package biblememorizer - 0.6.4-3build1
---
biblememorizer (0.6.4-3build1) precise; urgency=low
* Rebuild with libsword9 due to ABI breakage (LP: #935574)
- Temporarily bump libsword-dev build-dep version to prevent archive skew
-- Scott KittermanWe
This bug was fixed in the package bibletime - 2.8.1-2build1
---
bibletime (2.8.1-2build1) precise; urgency=low
* Rebuild with libsword9 due to ABI breakage (LP: #935574)
- Temporarily bump libsword-dev build-dep version to prevent archive skew
-- Scott KittermanWed, 11 Apr
I have access to an Ubuntu armel box. I'll try it and see.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/935574
Title:
ABI incompatability in libsword8 (xiphos segfaults)
To manage notifications a
** Changed in: sword (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/935574
Title:
ABI incompatability in libsword8 (xiphos segfaults)
To manage notifi
True, about armel. xiphos 3.1.5 did fail to build on armel in sid. But
at configure stage. I wonder if all dependencies are available. Didn't
have time to investigate yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
That seems fine then. I also test built it on Ubuntu i386 with the new sword
package and it builds fine. The remaining question is armel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/935574
Title:
(Upstream developer) 3.1.5 was primarily bug fixes and moving the backend
to Webkit.
On Wed, Apr 11, 2012 at 12:14 PM, Scott Kitterman
wrote:
> Are there any other new features in 3.1.5? If not, I agree syncing it
> sounds better.
>
> All the rebuilds are uploaded and waiting for the new sword,
3.1.5 really is:
* bugfixes
* drop xulrunner
* gain webkit
* gain gtk3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/935574
Title:
ABI incompatability in libsword8 (xiphos segfaults)
To manage noti
I noticed the new version is FTBFS on armel in Debian. That would have
to be addressed too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/935574
Title:
ABI incompatability in libsword8 (xiphos segf
Are there any other new features in 3.1.5? If not, I agree syncing it
sounds better.
All the rebuilds are uploaded and waiting for the new sword, but that
doesn't preclude syncing 3.1.5 if that seems like the right thing to do.
** Changed in: xiphos (Ubuntu)
Status: New => Fix Committed
Any chance of syncing newer xiphos 3.1.5+dfsg-1 as part of this?
Reasons:
* currently xiphos in precise is using gtkhtml backend, because xulrunner was
dropped
* 3.1.5+dfsg-1 has webkit backend which is better than obsolete xulrunner
backend
* webkit is the only backend support by upstream going
This bug was fixed in the package sword - 1.6.2+dfsg-3
---
sword (1.6.2+dfsg-3) unstable; urgency=low
* Fix FTBFS if running binary-arch target only.
-- Dmitrijs Ledkovs Mon, 09 Apr 2012 14:58:48 +0100
sword (1.6.2+dfsg-2) unstable; urgency=low
[ Dmitrijs Ledkovs ]
* Fix
For the record, this was discussed and agreed on #ubuntu-release among
the release team to go ahead with it.
** Also affects: bibletime (Ubuntu)
Importance: Undecided
Status: New
** Also affects: biblememorizer (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xipho
This is fixed in Debian now and we'll get it done for Precise as well.
** Changed in: sword (Ubuntu)
Status: Confirmed => In Progress
** Changed in: sword (Ubuntu)
Assignee: (unassigned) => Scott Kitterman (kitterman)
** Changed in: sword (Ubuntu)
Milestone: None => ubuntu-12.04
@roland: It isn't architecture specific, AFAIK. The problem is that the
API and ABI have changed, but it's still libsword.so.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/935574
Title:
ABI incompa
As a temporary workaround, I have libsword 1.6.1 in my foreports ppa
(ppa:ibid-ag/oldgtk1)
Note that that PPA is used for a number of packages that are older than
"current" or have been dropped from Ubuntu;
you may want to pin libsword, but probably not the PPA.
--
You received this bug notifi
Any clue if this will be fixed soon? I'm getting the problem on 32bit
only, and I have another system to upgrade to 12.04 soon...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/935574
Title:
ABI inco
I am getting a crash on start up using Precise on Xiphos... any ideas
when this fault will get fixed? I use Xiphos all the time... =(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/935574
Title:
ABI
http://pkg-
crosswire.alioth.debian.org/sword/1.6.1_to_1.6.2/abi_compat_report.html
ABI is incompatible =(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/935574
Title:
ABI incompatability in libswor
I haven't figured out the tools, but there are abi-compliance-checker,
abicheck, and icheck.
It looks like the abi is mostly the same (xsword compiled against 1.6.1 still
works), but there's one change that broke xiphos and apparently bibletime (from
what I hear)--so I suspect that recompiling r
Are you suggesting to recompile all reverse-deps on libsword8?
When I was packaging 1.6.2 I thought there is ABI change. Upstream /
other maintainers convinced me that there isn't. I guess there
actually is one.
Is there anyway to verify ABI change?
--
You received this bug notification bec
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sword (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/935574
Title:
ABI i
This is with Precise 12.04.
I thought that it was bug #783019, but it can't be since the incompatability
was introduced in Precise not Natty.
Xiphos works in Oneiric.
So: please do not mark as duplicate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
26 matches
Mail list logo
