Hiroyuki Yamamoto | 1 Feb 2005 04:12
Picon

[sylpheed:23923] Re: Sylpheed GTK2

Hello,

On Mon, 31 Jan 2005 14:54:33 +0100 (CET)
"Paul Kater" <paul <at> nlpagan.net> wrote:

> Is there a place where I can download a tar.gz or so for the GTK2 version
> of Sylpheed? I'd love to try it, but I can't find it. Maybe I missed or
> misunderstood something in how to get it?

Wait for the release I'll make today :-)

--

-- 
Hiroyuki Yamamoto <hiro-y <at> kcn.ne.jp>

Godwin Stewart | 1 Feb 2005 10:45
X-Face

[sylpheed:23924] Re: Sylpheed GTK2

On Tue, 1 Feb 2005 12:12:00 +0900, Hiroyuki Yamamoto <hiro-y <at> kcn.ne.jp>
wrote:

> Wait for the release I'll make today :-)

This is getting interesting!

Two milestones within the space of just over a month... Official 1.0.0
release on 2004-12-24 and now a GTK+2 release on 2005-02-01...

Not for nothing have I been using Sylpheed since version 0.5.2 or
thereabouts :)

--

-- 
G. Stewart - gstewart <at> bonivet.net

Mary had a little lamb which walked into a pylon
Ten thousand volts went up its  <at> $$ and turned its fleece to nylon
Hiroyuki Yamamoto | 1 Feb 2005 11:05
Picon

[sylpheed:23925] Sylpheed 1.9.0 (development) released

Hello,

Sylpheed 1.9.0 (development) has been released.

Please note that this is still a development version when you are going
to try it.

Changes:

    * The first release of the development version.
    * Migration to GTK2 has been made:
      - Multilingualization (m17n) has been supported.
      - The internal encoding has become UTF-8, including cache and
        configuration files.
      - Anti-aliased font display has been supported.
      - Many glitches related to font management have been solved.
      - The user-interface has been improved in many respects.
    * Gpgme-1.0 has been supported(thanks to Toshio Kuratomi).
      - A warning is displayed if a key for encryption is untrusted.
      - The status of signature validity became more descriptive.
      - Signatures inside nested multipart are now recognized.

--

-- 
Hiroyuki Yamamoto <hiro-y <at> kcn.ne.jp>

Hiroyuki Yamamoto | 1 Feb 2005 11:08
Picon

[sylpheed:23926] Sylpheed 1.0.1 (stable) released

Hello,

Sylpheed 1.0.1 (stable) has been released.

Changes:

    * Gpgme-1.0 has been supported (thanks to Toshio Kuratomi).
      - A warning is displayed if a key for encryption is untrusted.
      - The status of signature validity became more descriptive.
      - Signatures inside nested multipart are now recognized.
    * Messages are not retrieved multiple times anymore after POP3
      session is aborted.
    * Other bugfixes have been made.

--

-- 
Hiroyuki Yamamoto <hiro-y <at> kcn.ne.jp>

Angelo Secchi | 1 Feb 2005 11:34
X-Face
Picon
Favicon

[sylpheed:23927] Re: Sylpheed 1.9.0 (development) released


Thanks for your effort Hiroyuki.
It compiles and works great on a gentoo amd64 with gcc-3.4.3-r1 and gpgme-1.0.2.

--
========================================================
 Angelo Secchi                     PGP Key ID:EA280337
========================================================

On Tue, 1 Feb 2005 19:05:29 +0900
Hiroyuki Yamamoto <hiro-y <at> kcn.ne.jp> wrote:

> Hello,
> 
> Sylpheed 1.9.0 (development) has been released.
> 
> Please note that this is still a development version when you are going
> to try it.
> 
> Changes:
> 
>     * The first release of the development version.
>     * Migration to GTK2 has been made:
>       - Multilingualization (m17n) has been supported.
>       - The internal encoding has become UTF-8, including cache and
>         configuration files.
>       - Anti-aliased font display has been supported.
>       - Many glitches related to font management have been solved.
>       - The user-interface has been improved in many respects.
>     * Gpgme-1.0 has been supported(thanks to Toshio Kuratomi).
(Continue reading)

Attila Kinali | 1 Feb 2005 12:09
Picon

[sylpheed:23928] Re: Sylpheed GTK2

On Mon, 31 Jan 2005 20:42:13 +0000
rkimber <at> ntlworld.com wrote:

> > After installing proper development environment, its build can be done
> > 
> > by './autogen.sh && make'.
> 
> Not as user-friendly as making a snapshot available.
> - Richard.

You don't want mere users who are not able to use autogen.sh
to use development versions.
They simply cannot write usable bugreports and will be stuck
in problems of still developing features.

				Attila Kinali

--

-- 
郷に入れば郷に従え

Godwin Stewart | 1 Feb 2005 13:12
X-Face

[sylpheed:23929] Re: Sylpheed 1.9.0 (development) released

On Tue, 1 Feb 2005 19:05:29 +0900, Hiroyuki Yamamoto <hiro-y <at> kcn.ne.jp> 
wrote: 

> Sylpheed 1.9.0 (development) has been released.
> 
> Please note that this is still a development version when you are going to
> try it.

It compiled and runs great on FreeBSD 5.3-STABLE with one caveat so far that
I've seen.

If you reply to a post, the introduction "on $date, $sender wrote:" appears 
but there's nothing else copied into the buffer, and this is output to 
stderr multiple times:

(sylpheed:67652): Gtk-WARNING **: Invalid text buffer iterator: either the iterator is uninitialized,
or the characters/pixbufs/widgets in the buffer have been modified since the iterator was created.
You must use marks, character numbers, or line numbers to preserve a position across buffer modifications.
You can apply tags and insert marks without invalidating your iterators,
but any mutation that affects 'indexable' buffer contents (contents that can be referred to by character offset)
will invalidate all outstanding iterators

(sylpheed:67652): Gtk-CRITICAL **: file gtktextbuffer.c: line 591 (gtk_text_buffer_insert):
assertion `gtk_text_iter_get_buffer (iter) == buffer' failed

--

-- 
G. Stewart - gstewart <at> bonivet.net

What exactly does buildworld build anyway? If it really does build the
world then there's the mother of all bug reports to file somewhere!
(Continue reading)

Stephan Windmüller | 1 Feb 2005 14:01
Picon

[sylpheed:23930] Unable to compile with gpgme 1.0.2

Hello!

Today I wanted to compile Sylpheed 1.0.1 using my self-compiled gpgme
1.0.2. The configure-script does not complain, but during compile I get
the following errors:

---

main.o: In function `main':
/tmp/sylpheed/sylpheed-1.0.1/src/main.c:242: undefined reference to
`gpgme_set_locale'
/tmp/sylpheed/sylpheed-1.0.1/src/main.c:243: undefined reference to
`gpgme_set_locale'
/tmp/sylpheed/sylpheed-1.0.1/src/main.c:247: undefined reference to
`gpgme_get_protocol_name'
rfc2015.o: In function `sig_status_for_key':
/tmp/sylpheed/sylpheed-1.0.1/src/rfc2015.c:130: undefined reference to
`gpgme_get_key'
rfc2015.o: In function `check_signature':
/tmp/sylpheed/sylpheed-1.0.1/src/rfc2015.c:260: undefined reference to
`gpgme_op_verify_result'
rfc2015.o: In function `rfc2015_decrypt_message':
/tmp/sylpheed/sylpheed-1.0.1/src/rfc2015.c:614: undefined reference to
`gpgme_data_seek'
/tmp/sylpheed/sylpheed-1.0.1/src/rfc2015.c:614: undefined reference to
`gpgme_error_from_errno'
/tmp/sylpheed/sylpheed-1.0.1/src/rfc2015.c:626: undefined reference to
`gpgme_error_from_errno'
rfc2015.o: In function `pgp_encrypt':
/tmp/sylpheed/sylpheed-1.0.1/src/rfc2015.c:657: undefined reference to
(Continue reading)

Godwin Stewart | 1 Feb 2005 14:04
X-Face

[sylpheed:23931] Re: Unable to compile with gpgme 1.0.2

On Tue, 1 Feb 2005 14:01:16 +0100, Stephan Windmüller <windy <at> white-hawk.de>
wrote:

> What causes this error and what can I do to prevent it?

At a guess I'd say that you have more than one version of gpgme installed
and that the compile process is picking up the wrong one. Uninstall the old
one and the problem should go away.

-- 
G. Stewart - gstewart <at> bonivet.net

"I once had a rose named after me and I was very flattered. 
 But I was not pleased to read the description in the catalogue: 
 No good in a bed, but fine up against a wall."  
                  -- Eleanor Roosevelt 
Stephan Windmüller | 1 Feb 2005 14:30
Picon

[sylpheed:23932] Re: Unable to compile with gpgme 1.0.2

On Tue, 01. Feb 2005, Godwin Stewart wrote:

> > What causes this error and what can I do to prevent it?
> At a guess I'd say that you have more than one version of gpgme
> installed and that the compile process is picking up the wrong one.
> Uninstall the old one and the problem should go away.

That solved the problem. Thank you for the quick reply!

Regards
 Stephan

Gmane