Can we put links to the upstream bugs/patches (not to the rpms)
somewhere? In a README file or something. Right now if you want to
build Write on anything else than Fedora 18, you have no idea how to
do it.
Also a gtk2 branch would be nice to have since the gtk3 version will
not work on Ubuntu,
The problem is not Write, but Abiword, because we need a few patches under
review right now.
The gtk2 branch is origin/sugar-0.94 in Write and is available.
Gonzalo
On Wed, Oct 31, 2012 at 8:53 AM, Daniel Narvaez dwnarv...@gmail.com wrote:
Can we put links to the upstream bugs/patches (not to
Hi,
I know it's not Write. But Write has an undocumented dependency on a
certain Abiword version plus not yet up streamed patches.That's very
developer unfriendly. How am I'm supposed to pull the sources and get it to
work? That normally doesn't require subscribing to a mailing list and
asking.
On Wed, Oct 31, 2012 at 10:52 AM, Daniel Narvaez dwnarv...@gmail.comwrote:
Hi,
I know it's not Write. But Write has an undocumented dependency on a
certain Abiword version plus not yet up streamed patches.That's very
developer unfriendly. How am I'm supposed to pull the sources and get it to
On 31 October 2012 15:10, Gonzalo Odiard gonz...@laptop.org wrote:
On Wed, Oct 31, 2012 at 10:52 AM, Daniel Narvaez dwnarv...@gmail.com
wrote:
Hi,
I know it's not Write. But Write has an undocumented dependency on a
certain Abiword version plus not yet up streamed patches.That's very
On Wed, Oct 31, 2012 at 8:20 AM, Daniel Narvaez dwnarv...@gmail.com wrote:
I know you guys are busy and I don't want to keep wasting your time
(in this discussion too!). Though let me just suggest that putting
links to the upstream bugs in a text file wouldn't take much time.
Using a separate
On 22/10/2012 02:31, Gonzalo Odiard wrote:
Just for the record, on my i386, my rpmbuild --rebuild
abiword-2.9.3-1.git20121011.fc18.olpc2.src.rpm failed telling me
./.libs/libabiword-2.9.so http://libabiword-2.9.so: undefined
reference to '__atomic_fetch_add_4'.
I didn't
Has the patch been submitted upstream yet?
On Sunday, 21 October 2012, Gonzalo Odiard wrote:
Can you check the version of the Write activity you are using?
If the version is = 80, is a gtk3 version, and only will work
with the last abiword version, in fact, we are using a patched version
and
On Sun, Oct 21, 2012 at 5:50 AM, Daniel Narvaez dwnarv...@gmail.com wrote:
Has the patch been submitted upstream yet?
Gonzalo (and others) have been working with the upstream, I can't say
for sure about any specific patch.
AbiWord and Sugar have a long and productive history together (their
Part of the changes needed by touch interaction has not be reviewed yet
upstream,
and will not be ready for the next release. The plan is use a custom rpm
now,
and try to have the needed changes included asap to use a standard fedora
rpm.
Gonzalo
On Sun, Oct 21, 2012 at 6:50 AM, Daniel Narvaez
On 21/10/2012 04:53, Gonzalo Odiard wrote:
Can you check the version of the Write activity you are using?
If the version is = 80, is a gtk3 version, and only will work
with the last abiword version, in fact, we are using a patched version
and you download it
here
On 21/10/2012 21:04, Coltivare Fiori wrote:
On 21/10/2012 04:53, Gonzalo Odiard wrote:
Can you check the version of the Write activity you are using?
If the version is = 80, is a gtk3 version, and only will work
with the last abiword version, in fact, we are using a patched version
and you
Just for the record, on my i386, my rpmbuild --rebuild
abiword-2.9.3-1.git20121011.fc18.olpc2.src.rpm failed telling me
./.libs/libabiword-2.9.so: undefined reference to
'__atomic_fetch_add_4'.
I didn't expect my compilation to go *that* far anyway, so I'm very
happy :-)) You Sugar
Can you check the version of the Write activity you are using?
If the version is = 80, is a gtk3 version, and only will work
with the last abiword version, in fact, we are using a patched version
and you download it here
http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=1205046
Gonzalo
On
14 matches
Mail list logo
