Re: upset messages

Re: upset messages

[Corinna Vinschen]

On Nov  9 10:36, <annoying raw email address> wrote:
> upset: *** /var/ftp/pub/cygwin/x86/setup.ini: error - package gcc-java requires nonexistent package java-ecj
> upset: *** /var/ftp/pub/cygwin/x86/setup.ini: error - package gcc-java requires package java-ecj which has no "curr" binary

I silenced this message for now by removing the nonexisting java-ecj from
gcc/gcc-java/setup.hint, but this looks wrong.


Corinna

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: upset messages

[JonY]

[-- Attachment #1: Type: text/plain, Size: 610 bytes --]

On 11/9/2013 18:45, Corinna Vinschen wrote:
> On Nov  9 10:36, <annoying raw email address> wrote:
>> upset: *** /var/ftp/pub/cygwin/x86/setup.ini: error - package gcc-java requires nonexistent package java-ecj
>> upset: *** /var/ftp/pub/cygwin/x86/setup.ini: error - package gcc-java requires package java-ecj which has no "curr" binary
> 
> I silenced this message for now by removing the nonexisting java-ecj from
> gcc/gcc-java/setup.hint, but this looks wrong.
> 

Thanks, already asked Yaakov to put up gcc-ecj, since he already has it
in Cygwin ports.

What about the odd gcc4 warning?



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 834 bytes --]

Re: upset messages

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 983 bytes --]

On Nov  9 21:20, JonY wrote:
> On 11/9/2013 18:45, Corinna Vinschen wrote:
> > On Nov  9 10:36, <annoying raw email address> wrote:
> >> upset: *** /var/ftp/pub/cygwin/x86/setup.ini: error - package gcc-java requires nonexistent package java-ecj
> >> upset: *** /var/ftp/pub/cygwin/x86/setup.ini: error - package gcc-java requires package java-ecj which has no "curr" binary
> > 
> > I silenced this message for now by removing the nonexisting java-ecj from
> > gcc/gcc-java/setup.hint, but this looks wrong.
> > 
> 
> Thanks, already asked Yaakov to put up gcc-ecj, since he already has it
> in Cygwin ports.

Guess you mean java-ecj...

> What about the odd gcc4 warning?

Should be fixed.  I removed gcc4/libstdc++-devel.

My reply a couple of hours ago was just catched by this #$%@ raw email
address filter.  I'd really appreciate if we could go along without this
aggressive email blocking.  It's getting more annoying than helpful,
lately.


Corinna

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: upset messages

[JonY]

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

On 11/10/2013 00:51, Corinna Vinschen wrote:
> On Nov  9 21:20, JonY wrote:
>> On 11/9/2013 18:45, Corinna Vinschen wrote:
>>> On Nov  9 10:36, <annoying raw email address> wrote:
>>>> upset: *** /var/ftp/pub/cygwin/x86/setup.ini: error - package gcc-java requires nonexistent package java-ecj
>>>> upset: *** /var/ftp/pub/cygwin/x86/setup.ini: error - package gcc-java requires package java-ecj which has no "curr" binary
>>>
>>> I silenced this message for now by removing the nonexisting java-ecj from
>>> gcc/gcc-java/setup.hint, but this looks wrong.
>>>
>>
>> Thanks, already asked Yaakov to put up gcc-ecj, since he already has it
>> in Cygwin ports.
> 
> Guess you mean java-ecj...
> 

Yes, java-ecj, sorry.

>> What about the odd gcc4 warning?
> 
> Should be fixed.  I removed gcc4/libstdc++-devel.
> 

Thanks.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 834 bytes --]

Re: upset messages

[Christopher Faylor]

On Sat, Nov 09, 2013 at 05:51:34PM +0100, Corinna Vinschen wrote:
>My reply a couple of hours ago was just catched by this #$%@ raw email
>address filter.  I'd really appreciate if we could go along without this
>aggressive email blocking.  It's getting more annoying than helpful,
>lately.

The raw email filter was working effectively in this case.  You would
have sent a raw cygwin mailing list address if you hadn't been blocked.

So, without the filter, you would have exposed the cygwin mailing list
address and potentially had people tell you PCYMTNQREAIYR (something
which you, yourself, do fairly often).  Sparing the list that traffic
and not adding one more place for spammers is pretty helpful.

But even with that aside, the fact is that you have no way of knowing
how helpful the block is because you only see a bounce when it affects
your sending of email.  I, on the other hand, see the people trying to
send email with corinna-cygwin or lh-cygwin in the body.  It doesn't get
through and, so, often, people decide to send email to the cygwin list
instead, as we require.  I also see the messages which include
cygwin-owner and cygwin in their body, of course.

I know that some of the above could actually be considered a false
positive since neither corinna-cygwin nor lh-cygwin are not what the
block was theoretically supposed to catch but since they fall under
PCYMTNQREAIYR, I have never tried to tighten the filter up.

Finally, "upset messages" discussions are off-topic for this list
anyway.  I understand why they ended up here since I have done the same
thing myself.  I think I've fixed that problem.  I've made modifications
to upset to set the Reply-To to the list of maintainers so replying to
the upset mail (which comes from the cygwin account on sourceware)
should no longer cause email to be sent here.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple