Thread: [Mesa3d-dev] Commit messages broken??

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

I haven't seen any of these for a while now...  Anyone have any ideas?

Keith

Keith Whitwell wrote:
> I haven't seen any of these for a while now...  Anyone have any ideas?

I haven't seen them either.  I don't know what's going on, but Tollef 
Fog Heen (an FD.org admin) created new mesa lists on fd.o yesterday 
(though Michel and I haven't move the subscriber lists yet).  Perhaps 
something broke from that?

Tollef?

-Brian

Brian Paul wrote:
> Keith Whitwell wrote:
>> I haven't seen any of these for a while now...  Anyone have any ideas?
> 
> I haven't seen them either.  I don't know what's going on, but Tollef 
> Fog Heen (an FD.org admin) created new mesa lists on fd.o yesterday 
> (though Michel and I haven't move the subscriber lists yet).  Perhaps 
> something broke from that?
> 
> Tollef?

It looks like the list itself is OK but the git trigger to send out 
the commit messages isn't working.

Do any git experts know what might be wrong?

-Brian

On Wednesday 10 March 2010 14:59:42 Zack Rusin wrote:
> Maybe /usr/bin/mail is broken, I'll double check it.

Yea, that's it. Someone installed a new mail daemon on the server. We're using 
"-a" to specify the Content-Type header in mails, but the heirloom mailx that 
has been installed uses the "-a" option to specify attachments and since 
filename "Content-Type: text/plain;" is not a valid filename it exits with an 
error. I'll try to fix it right now.
BTW, replacing a mail client on the server with something that's not 
compatible is not very social.

z

On Wednesday 10 March 2010 15:18:03 Zack Rusin wrote:
> On Wednesday 10 March 2010 14:59:42 Zack Rusin wrote:
> > Maybe /usr/bin/mail is broken, I'll double check it.
> 
> Yea, that's it. Someone installed a new mail daemon on the server. We're
>  using "-a" to specify the Content-Type header in mails, but the heirloom
>  mailx that has been installed uses the "-a" option to specify attachments
>  and since filename "Content-Type: text/plain;" is not a valid filename it
>  exits with an error. I'll try to fix it right now.

k, it should be working now. I switched it to use sendmail directly so that 
future changes to /usr/bin/mail don't affect it.

z

Zack Rusin wrote:
> On Wednesday 10 March 2010 15:18:03 Zack Rusin wrote:
>> On Wednesday 10 March 2010 14:59:42 Zack Rusin wrote:
>>> Maybe /usr/bin/mail is broken, I'll double check it.
>> Yea, that's it. Someone installed a new mail daemon on the server. We're
>>  using "-a" to specify the Content-Type header in mails, but the heirloom
>>  mailx that has been installed uses the "-a" option to specify attachments
>>  and since filename "Content-Type: text/plain;" is not a valid filename it
>>  exits with an error. I'll try to fix it right now.
> 
> k, it should be working now. I switched it to use sendmail directly so that 
> future changes to /usr/bin/mail don't affect it.

Thanks, Zack!!

-Brian

On Wednesday 10 March 2010 13:59:40 Brian Paul wrote:
> Brian Paul wrote:
> > Keith Whitwell wrote:
> >> I haven't seen any of these for a while now...  Anyone have any ideas?
> >
> > I haven't seen them either.  I don't know what's going on, but Tollef
> > Fog Heen (an FD.org admin) created new mesa lists on fd.o yesterday
> > (though Michel and I haven't move the subscriber lists yet).  Perhaps
> > something broke from that?
> >
> > Tollef?
> 
> It looks like the list itself is OK but the git trigger to send out
> the commit messages isn't working.
> 
> Do any git experts know what might be wrong?

I wrote that script and looked at it yesterday and I don't see what's wrong. 
The script uses /usr/bin/mail to send those mails. Has something changed on 
the server? Maybe /usr/bin/mail is broken, I'll double check it.

On Wed, Mar 10, 2010 at 12:59 PM, Zack Rusin <za...@vm...> wrote:

> On Wednesday 10 March 2010 13:59:40 Brian Paul wrote:
> > Brian Paul wrote:
> > > Keith Whitwell wrote:
> > >> I haven't seen any of these for a while now...  Anyone have any ideas?
> > >
> > > I haven't seen them either.  I don't know what's going on, but Tollef
> > > Fog Heen (an FD.org admin) created new mesa lists on fd.o yesterday
> > > (though Michel and I haven't move the subscriber lists yet).  Perhaps
> > > something broke from that?
> > >
> > > Tollef?
> >
> > It looks like the list itself is OK but the git trigger to send out
> > the commit messages isn't working.
> >
> > Do any git experts know what might be wrong?
>
> I wrote that script and looked at it yesterday and I don't see what's
> wrong.
> The script uses /usr/bin/mail to send those mails. Has something changed on
> the server? Maybe /usr/bin/mail is broken, I'll double check it.
>
>
I can see the headline now:

Mesa3d-dev Mail Mauled by Mangey Monster

and it's no surprise Zack jumps to the rescue, given his background with
monsters.

On Wed, Mar 10, 2010 at 11:59 AM, Zack Rusin <za...@vm...> wrote:
> On Wednesday 10 March 2010 13:59:40 Brian Paul wrote:
>> Brian Paul wrote:
>> > Keith Whitwell wrote:
>> >> I haven't seen any of these for a while now...  Anyone have any ideas?
>> >
>> > I haven't seen them either.  I don't know what's going on, but Tollef
>> > Fog Heen (an FD.org admin) created new mesa lists on fd.o yesterday
>> > (though Michel and I haven't move the subscriber lists yet).  Perhaps
>> > something broke from that?
>> >
>> > Tollef?
>>
>> It looks like the list itself is OK but the git trigger to send out
>> the commit messages isn't working.
>>
>> Do any git experts know what might be wrong?
>
> I wrote that script and looked at it yesterday and I don't see what's wrong.
> The script uses /usr/bin/mail to send those mails. Has something changed on
> the server? Maybe /usr/bin/mail is broken, I'll double check it.

Maybe the mesa-commit subscriber/whitelist configuration got
overwritten in the list conversion and the user sending the commit
messages is not allowed to post anymore. You could look in the
moderation queue.

--
Dan

]] Zack Rusin 

| On Wednesday 10 March 2010 14:59:42 Zack Rusin wrote:
| > Maybe /usr/bin/mail is broken, I'll double check it.
| 
| Yea, that's it. Someone installed a new mail daemon on the
| server. We're using "-a" to specify the Content-Type header in mails,
| but the heirloom mailx that has been installed uses the "-a" option to
| specify attachments and since filename "Content-Type: text/plain;" is
| not a valid filename it exits with an error. I'll try to fix it right
| now.

Ah, that would be it.  (And mail(1) is hardly a mail daemon :-)

| BTW, replacing a mail client on the server with something that's not 
| compatible is not very social.

Rather than assuming malice, you may assume that I was trying to fix
something when I made that change.  The old mailx mangled UTF-8
content.  The easiest way around this is to use /usr/bin/bsd-mailx
rather than just mail.  I believe it just does the right thing wrt
content-type now, so just dropping -a should fix it.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

On Thursday 11 March 2010 02:58:49 Tollef Fog Heen wrote:
> ]] Zack Rusin 
> | BTW, replacing a mail client on the server with something that's not
> | compatible is not very social.
> 
> Rather than assuming malice, you may assume that I was trying to fix
> something when I made that change.  

I was assuming that whoever did it was trying to do something, but the 
reasoning behind the change doesn't change the result at all - we were not 
informed of it and the commit messages broke. So as far as we are concerned 
there really wouldn't be any difference between someone just deleting 
/usr/bin/mail and you trying to fix something by replacing mail with something 
else. The bottom line is that there's quite a few projects hosted on fdo, with 
a lot of people depending on that setup and making changes to it without 
communicating it very clearly it is bound to break something.
I don't want to make into a big deal, because it wasn't but a short email or 
even an blog just saying "new /usr/bin/mail is coming in, make sure it doesn't 
break your project" would avoid the whole problem.

z

On Thu, Mar 11, 2010 at 10:02:46AM -0500, Zack Rusin wrote:
> On Thursday 11 March 2010 02:58:49 Tollef Fog Heen wrote:
> > ]] Zack Rusin 
> > | BTW, replacing a mail client on the server with something that's not
> > | compatible is not very social.
> > 
> > Rather than assuming malice, you may assume that I was trying to fix
> > something when I made that change.  
> 
> I was assuming that whoever did it was trying to do something, but the 
> reasoning behind the change doesn't change the result at all - we were not 
> informed of it and the commit messages broke. So as far as we are concerned 
> there really wouldn't be any difference between someone just deleting 
> /usr/bin/mail and you trying to fix something by replacing mail with something 
> else. The bottom line is that there's quite a few projects hosted on fdo, with 
> a lot of people depending on that setup and making changes to it without 
> communicating it very clearly it is bound to break something.
> I don't want to make into a big deal, because it wasn't but a short email or 
> even an blog just saying "new /usr/bin/mail is coming in, make sure it doesn't 
> break your project" would avoid the whole problem.

Shit happens.  Ease up.

On Thu, Mar 11, 2010 at 7:10 AM, Daniel Stone <da...@fo...> wrote:
> On Thu, Mar 11, 2010 at 10:02:46AM -0500, Zack Rusin wrote:
>> On Thursday 11 March 2010 02:58:49 Tollef Fog Heen wrote:
>> > ]] Zack Rusin
>> > | BTW, replacing a mail client on the server with something that's not
>> > | compatible is not very social.
>> >
>> > Rather than assuming malice, you may assume that I was trying to fix
>> > something when I made that change.
>>
>> I was assuming that whoever did it was trying to do something, but the
>> reasoning behind the change doesn't change the result at all - we were not
>> informed of it and the commit messages broke. So as far as we are concerned
>> there really wouldn't be any difference between someone just deleting
>> /usr/bin/mail and you trying to fix something by replacing mail with something
>> else. The bottom line is that there's quite a few projects hosted on fdo, with
>> a lot of people depending on that setup and making changes to it without
>> communicating it very clearly it is bound to break something.
>> I don't want to make into a big deal, because it wasn't but a short email or
>> even an blog just saying "new /usr/bin/mail is coming in, make sure it doesn't
>> break your project" would avoid the whole problem.
>
> Shit happens.  Ease up.

Not to fan the flames anymore, but there is the fd.o administration
blog that's syndicated on planet. That would be a nice place to dump
information like this, and IIRC Benjamin used to do that. However, it
seems that www.freedesktop.org/adminblog/ doesn't have the necessary
permissions to view the entries.

--
Dan

Thread: [Mesa3d-dev] Commit messages broken??

mesa3d-dev