Kevin B wrote:
> <some uninteresting stuff>

> See the text attachment.

NO binaries please.
Perhaps there's something else going on: you don't know how to behave in
the different media.

--
Rik Wasmus

Looks like the info is being supressed here too. So much for free
speech on the "different media".

Its OK, I got
"Seagullframework" at groups.yahoo.com
and
"seagullframework-bugs" at groups.google.com

For people who want the real story on the bug.

Sorry Rik, you can suppress this post, but not those.

On Jan 18, 9:12 am, "Rik" <luiheidsgoe... [at] hotmail.com> wrote:
> Kevin B wrote:
> > <some uninteresting stuff>
> > See the text attachment.NO binaries please.
> Perhaps there's something else going on: you don't know how to behave in
> the different media.
>
> --
> Rik Wasmus

Further evidence that Seagull developers are wrong:

# for i in `rpm -q -l php-pear`; do grep -l mbstring $i ; done | less

/usr/share/pear/.registry/xml_rpc.reg
/usr/share/pear/XML/RPC.php


See original thread at:
http://groups.google.com/group/seagullframework-bugs/browse_ frm/thread/1f5b8224189d205e

This final post represents that php-mbstring is required by php-pear
which is being used by Seagull Framwork, which is not being checked by
the installer program (to see if php-mbstring is being installed).

Ok Seagull Framework folks, you can apologize now.

(See original rant: http://tech.groups.yahoo.com/group/seagullframework
)


Let's drive the bus all the way home for these programmers in denial:
# grep RPC.php /var/www/seagull/*/*/*/*
/var/www/seagull/lib/pear/PEAR/Remote.php: } elseif (!($fp =
fopen('XML/RPC.php', 'r', true))) {
/var/www/seagull/lib/pear/PEAR/Remote.php: include_once
'XML/RPC.php';
/var/www/seagull/lib/pear/XML/RPC.php: * [at] version CVS: $Id:RPC.php,v
1.101 2006/10/28 16:42:34 danielc Exp $


Kevin wrote:
> Further evidence that Seagull developers are wrong:
>
> # for i in `rpm -q -l php-pear`; do grep -l mbstring $i ; done | less
>
> /usr/share/pear/.registry/xml_rpc.reg
> /usr/share/pear/XML/RPC.php
>
>
> See original thread at:
> http://groups.google.com/group/seagullframework-bugs/browse_ frm/thread/1f5b8224189d205e

Me wrote:
> Looks like the info is being supressed here too. So much for free
> speech on the "different media".
>
> Its OK, I got
> "Seagullframework" at groups.yahoo.com
> and
> "seagullframework-bugs" at groups.google.com
>
> For people who want the real story on the bug.
>
> Sorry Rik, you can suppress this post, but not those.

Huh? I can censor alt.php? Great! Tell me how, then I'll kill the
irritating "Pingey: Spacy Girl" and "FUSK!" thread this very instant....

If this is the way people 'surpressed' your message, I'd say someone is not
a 100%. And if you just ranted about this framework _without_ posting a
binary I wouldn't even have bothered answering it. I have not interest in
seagull or any other framework for that matter at this moment, and I
suspect for a long time to come.
--
Rik Wasmus

Another Seagull bug:
It's nice to know, that I'm not the only one who makes grammatical
mistakes from time to time. Here's another Seagull bug. Permanently
what'ed?

ERROR: You have been banned.
Your account was permanently from accessing the site, due to a
violation of the forum's rules.