Web Server Back Online

[Jeremy Newman]

The webserver is back online. There are still plenty of quirks to fix.
Feel free to bug me here on wine-devel about any issues that crop up.

Whats Up:
www.winehq.org website
bugs.winehq.org website
appdb.winehq.org website
FTP site
Anonymous CVS access

What is still down:
We use cvsupd to sync our CVS trees. I'm still working on getting this
running on Debian Sarge. It is no longer included in Sarge so I
installed the woody packages. Though I have been unable to get it
working. What this means is any commits that Alexander makes will not
get into the anonymous tree until I figure it out.

ChangeLog:
- moved OS to Debian Sarge
* now using - Apache 2.0.54 / PHP 4.3.10
* switched from sendmail to Exim4
* upgraded mailing lists from mailman 2.0 to 2.1
* mailing lists now using pipermail for archiving
   note: old links will work as the hypermail archives still exist

I'm still tweaking configs and all so expect the site to be a bit
erratic over the next few days.

[Alex Villací­s Lasso]

Jeremy Newman wrote:
> The webserver is back online. There are still plenty of quirks to fix.
> Feel free to bug me here on wine-devel about any issues that crop up.
>
> Whats Up:
> www.winehq.org website
> bugs.winehq.org website
> appdb.winehq.org website
> FTP site
> Anonymous CVS access

Anonymous CVS still doesn't work for me:

[alex@srv64 src-python]$ cd ~/download/wine/wine-20050725-cvs/
[alex@srv64 wine-20050725-cvs]$ cvs update -PAd
/home/wine: no such repository
[alex@srv64 wine-20050725-cvs]$ cvs login
Logging in to :pserver:[e-mail]:2401/home/wine
CVS password:
/home/wine: no such repository
[alex@srv64 wine-20050725-cvs]$

I can only assume that the repository is no longer at /home/wine, but 
this is the announced path on the website, and it has worked until today.
So, which is the new path, if any?

Alex Villacís Lasso

[Jeremy Newman]

It works. You are probably still resolving to the old IP. That should
clear up shortly.

$ host winehq.org
winehq.org has address 209.32.141.3

$ cvs -d:pserver:[e-mail]:/home/wine co wine
cvs checkout: Updating wine
U wine/.cvsignore
U wine/ANNOUNCE
U wine/AUTHORS
...

On Tue, 2005-08-30 at 18:44 -0500, Alex Villací­s Lasso wrote:
> Jeremy Newman wrote:
> > The webserver is back online. There are still plenty of quirks to fix.
> > Feel free to bug me here on wine-devel about any issues that crop up.
> >
> > Whats Up:
> > www.winehq.org website
> > bugs.winehq.org website
> > appdb.winehq.org website
> > FTP site
> > Anonymous CVS access
>
> Anonymous CVS still doesn't work for me:
>
> [alex@srv64 src-python]$ cd ~/download/wine/wine-20050725-cvs/
> [alex@srv64 wine-20050725-cvs]$ cvs update -PAd
> /home/wine: no such repository
> [alex@srv64 wine-20050725-cvs]$ cvs login
> Logging in to :pserver:[e-mail]:2401/home/wine
> CVS password:
> /home/wine: no such repository
> [alex@srv64 wine-20050725-cvs]$
>
> I can only assume that the repository is no longer at /home/wine, but 
> this is the announced path on the website, and it has worked until today.
> So, which is the new path, if any?
>
> Alex Villacís Lasso

[Alex Villací­s Lasso]

Jeremy Newman wrote:
> It works. You are probably still resolving to the old IP. That should
> clear up shortly.
>
> $ host winehq.org
> winehq.org has address 209.32.141.3
>
> $ cvs -d:pserver:[e-mail]:/home/wine co wine
> cvs checkout: Updating wine
> U wine/.cvsignore
> U wine/ANNOUNCE
> U wine/AUTHORS
> ...

Oh, I see. The CVS repository is now at plain "winehq.org", instead of 
"cvs.winehq.org". I was getting confused, especially since the website 
has not changed to announce this change. Thanks for the explanation.

Alex Villacís Lasso

[Jeremy Newman]

Well, cvs.winehq.org is just a CNAME to www.winehq.org. They all point
to the same IP. Any of those hosts should work. Depending of course on
any stale DNS records at your name server. We prefer you use
cvs.winehq.org just in case down the road we do move it to a different
box or what have you.

On Tue, 2005-08-30 at 19:27 -0500, Alex Villací­s Lasso wrote:
> Oh, I see. The CVS repository is now at plain "winehq.org", instead of 
> "cvs.winehq.org". I was getting confused, especially since the website 
> has not changed to announce this change. Thanks for the explanation.

[Jeremy Newman]

On Tue, 2005-08-30 at 18:30 -0500, Jeremy Newman wrote:
> What is still down:
> We use cvsupd to sync our CVS trees. I'm still working on getting this
> running on Debian Sarge. It is no longer included in Sarge so I
> installed the woody packages. Though I have been unable to get it
> working. What this means is any commits that Alexander makes will not
> get into the anonymous tree until I figure it out.

This is fixed now. Anyone using cvsup can connect to the box again.
Commits from Alexander will sync back into the anonymous tree as well.

It is always a good time trying to re-learn how to configure something
you setup 5 years ago. :-)

[Vitaliy Margolen]

Tuesday, August 30, 2005, 5:30:49 PM, Jeremy Newman wrote:
> The webserver is back online. There are still plenty of quirks to fix.
> Feel free to bug me here on wine-devel about any issues that crop up.

It looks like pipermail doesn't understand some files and converts them to
something.bin, which makes it hard to read.

Here is an example: http://www.winehq.com/pipermail/wine-patches/2005-August/020339.html
The file included should be sync.diff

Vitaliy

[Jeremy Newman]

Interesting. Pipermail does not have any config that I can see to change
that. Looking at other mailing lists it looks like that is just how it
works.

On Tue, 2005-08-30 at 20:30 -0600, Vitaliy Margolen wrote:
> Tuesday, August 30, 2005, 5:30:49 PM, Jeremy Newman wrote:
> > The webserver is back online. There are still plenty of quirks to fix.
> > Feel free to bug me here on wine-devel about any issues that crop up.
>
> It looks like pipermail doesn't understand some files and converts them to
> something.bin, which makes it hard to read.
>
> Here is an example: http://www.winehq.com/pipermail/wine-patches/2005-August/020339.html
> The file included should be sync.diff
>
> Vitaliy

[Saulius Krasuckas]

* On Wed, 31 Aug 2005, Jeremy Newman wrote:
> - On Tue, 2005-08-30 at 20:30 -0600, Vitaliy Margolen wrote:
> > It looks like pipermail doesn't understand some files and converts 
> > them to something.bin, which makes it hard to read.
> >
> > Here is an example: 
> > http://www.winehq.com/pipermail/wine-patches/2005-August/020339.html 
> > The file included should be sync.diff
>
> Interesting. Pipermail does not have any config that I can see to change 
> that. Looking at other mailing lists it looks like that is just how it 
> works.

Hm.  The page shows it's type as "x-patch".  Even pine on my mail server 
knows it is a text file which can be easily viewed.  Still winehq 
server/mail-manager converts the type to "application/octet-stream".

$ wget -S http://www.winehq.org/pipermail/wine-patches/attachments/20050831/cb1e3bc5/s...
| --19:14:58--  http://www.winehq.org/pipermail/wine-patches/attachments/20050831/cb1e3bc5/s...
|            => `sync.bin'
| Resolving www.winehq.org... 209.32.141.3
| Connecting to www.winehq.org[209.32.141.3]:80... connected.
| HTTP request sent, awaiting response...
|  1 HTTP/1.1 200 OK
|  2 Date: Wed, 31 Aug 2005 16:16:06 GMT
|  3 Server: Apache/2.0.54 (Debian GNU/Linux)
|  4 Last-Modified: Wed, 31 Aug 2005 01:49:20 GMT
|  5 ETag: "5cd56-80e-efe46800"
|  6 Accept-Ranges: bytes
|  7 Content-Length: 2062
|  8 Keep-Alive: timeout=15, max=100
|  9 Connection: Keep-Alive
| 10 Content-Type: application/octet-stream

May it have something to do with the content of /etc/mime* ?

[Jeremy Newman]

On Wed, 2005-08-31 at 19:24 +0300, Saulius Krasuckas wrote:
> Hm.  The page shows it's type as "x-patch".  Even pine on my mail server 
> knows it is a text file which can be easily viewed.  Still winehq 
> server/mail-manager converts the type to "application/octet-stream".
> May it have something to do with the content of /etc/mime* ?

No, it's simple really. Pipermail stores all attachments in as .bin files. I believe this is to prevent any
possible server hacks by emailing attachments that could get executed locally by the server.
This was possible in hypermail by emailing a .cgi or a .php file. When you click that link the file would be executed.
I worked around it by disabling those extensions in the directories where hypermail is.

When you click the link, apache sees .bin, which will always return a mime type of application/octet-stream.

The only way to work around that is for pipermail to use a cgi program which would send the correct mime type when you download a file.

[Saulius Krasuckas]

* On Wed, 31 Aug 2005, Jeremy Newman wrote:
> - On Wed, 2005-08-31 at 19:24 +0300, Saulius Krasuckas wrote:
> > Still winehq server/mail-manager converts the type to 
> > "application/octet-stream".
>
> Pipermail stores all attachments in as .bin files. 
> ..
> When you click the link, apache sees .bin, which will always return a 
> mime type of application/octet-stream.

Ok, I am still new to apache. :-]

I wonder, can't Pipermail store all attachments here as .diff files?  
BTW, that would encourange users not to send .bz2 files. :-P
> The only way to work around that is for pipermail to use a cgi program 
> which would send the correct mime type when you download a file.

What programming language would be appropriate here?
And how much lines approximately would such program take?

[Jeremy Newman]

On Thu, 2005-09-01 at 12:18 +0300, Saulius Krasuckas wrote:
> - On Wed, 31 Aug 2005, Jeremy Newman wrote:
> > - On Wed, 2005-08-31 at 19:24 +0300, Saulius Krasuckas wrote:
> > The only way to work around that is for pipermail to use a cgi program 
> > which would send the correct mime type when you download a file.
>
> What programming language would be appropriate here?
> And how much lines approximately would such program take?

If you are serious about taking on this issue. The best place to go is
to check out the mailman CVS at:
http://www.gnu.org/software/mailman/

Mailman (and Pipermail) are written in Python. I have no idea how many
lines this would take, but it shouldn't be all that hard.

Please note, as policy I only use binary packages in the Debian stable
tree. So even if your patch gets approved I won't see it until the next
Debian goes stable. That would be 'etch' BTW.

[Saulius Krasuckas]

* On Thu, 1 Sep 2005, Jeremy Newman wrote:
> - On Thu, 2005-09-01 at 12:18 +0300, Saulius Krasuckas wrote:
>
> If you are serious about taking on this issue. The best place to go is
> to check out the mailman CVS at:
> http://www.gnu.org/software/mailman/

Thanks.
> as policy I only use binary packages in the Debian stable tree. So even 
> if your patch gets approved I won't see it until the next Debian goes 
> stable. That would be 'etch' BTW.

This means all the world is restricted from reading about a half of sent 
patches through a web for some lengthy time, maybe a year.  Right? :-(

OTOH, maybe my FF can be configured to treat *.bin files from winehq.org 
as .diff files (X-PATCH).  If someone know of such solution, alert me, 
please.

[Ron Jensen]

In reading the FAQ at http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.046.htp
I came to the impression that the mime-type and extension must match.  If they don't
the extension is changed to .bin.

I checked /etc/mime.types on my etch system and there is no text/x-patch.  'diff' is listed
as a file type under text/plain.

As an experiment I am attaching an ASCII text file to this e-mail with a .txt and a .diff 
extention, each file will get a mime type of text/plain and text/x-patch.

Let's see what mailman does...

Ron

[Jeremy Newman]

Interesting, when it does get the mime type, it inlines it for text
types. I'll add the mime type text/x-diff to /etc/mime.types and see
what happens.

Please try this email test again in about 5 minutes.

I'm not sure if people want the patches inline, maybe they do? Let me
know.

On Thu, 2005-09-01 at 11:40 -0600, Ron Jensen wrote:
> In reading the FAQ at http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.046.htp
> I came to the impression that the mime-type and extension must match.  If they don't
> the extension is changed to .bin.
>
> I checked /etc/mime.types on my etch system and there is no text/x-patch.  'diff' is listed
> as a file type under text/plain.
>
> As an experiment I am attaching an ASCII text file to this e-mail with a .txt and a .diff 
> extention, each file will get a mime type of text/plain and text/x-patch.
>
> Let's see what mailman does...
>
> Ron

[Richard Cohen]

Jeremy Newman wrote:
> Interesting, when it does get the mime type, it inlines it for text
> types. I'll add the mime type text/x-diff to /etc/mime.types and see
> what happens.

Dont't you mean text/x-patch?

Richard

[Jeremy Newman]

Right, I added both. Since some pass it as text/x-patch, and some pass
text/x-diff.

I haven't seen any complaints about the patches appearing inline, so I
assume that it is OK.

On Thu, 2005-09-01 at 23:43 +0100, Richard Cohen wrote:
> Jeremy Newman wrote:
> > Interesting, when it does get the mime type, it inlines it for text
> > types. I'll add the mime type text/x-diff to /etc/mime.types and see
> > what happens.
>
> Dont't you mean text/x-patch?
>
> Richard

[Saulius Krasuckas]

* On Thu, 1 Sep 2005, Jeremy Newman wrote:
> - On Thu, 2005-09-01 at 23:43 +0100, Richard Cohen wrote:
> > Dont't you mean text/x-patch?
>
> Right, I added both. Since some pass it as text/x-patch, and some pass 
> text/x-diff.

\m/
Works fine for me.  Big thanks.

[Saulius Krasuckas]

* On Fri, 2 Sep 2005, Saulius Krasuckas wrote:
> - On Thu, 1 Sep 2005, Jeremy Newman wrote:
> > - On Thu, 2005-09-01 at 23:43 +0100, Richard Cohen wrote:
> > > Dont't you mean text/x-patch?
> >
> > Right, I added both. Since some pass it as text/x-patch, and some pass 
> > text/x-diff.
>
> Works fine for me.  Big thanks.

It stopped working nice for me again.  The server returns "Content-Type: 
text/x-diff" in the HTTP headers, but somehow all my browsers started 
asking me about what should they do with such file.

Any ideas, why?  What have changed since then?

[Ron Jensen]

Sorry it took longer to retry the test.  Had to work some.

Let's see what mailman does this time...

Ron

[Jeremy White]

Jeremy Newman wrote:
> The webserver is back online. There are still plenty of quirks to fix.
> Feel free to bug me here on wine-devel about any issues that crop up.

Just because no one else has said it yet:

Nice work, Jer!

(Jer is masking all the behind the scenese wrangling
he did with our two ISPs to arrange this, and the
mad scramble to replace a raided drive that
had fried, and the rebuild to Debian.  )

It was darn nice work on his part to get it all essentially
done in a day.

Cheers,

Jeremy

[Tom Wickline]

On 8/30/05, Jeremy White  wrote:
> Jeremy Newman wrote:
> > The webserver is back online. There are still plenty of quirks to fix.
> > Feel free to bug me here on wine-devel about any issues that crop up.
>
> Just because no one else has said it yet:
>
> Nice work, Jer!

http://www.winehq.org/  doesn't work here......

http://winehq.org/  works fine ;-)

Tom

[Tom Wickline]

On 8/31/05, Tom Wickline  wrote:
> On 8/30/05, Jeremy White  wrote:
> > Jeremy Newman wrote:
> > > The webserver is back online. There are still plenty of quirks to fix.
> > > Feel free to bug me here on wine-devel about any issues that crop up.
> >
> > Just because no one else has said it yet:
> >
> > Nice work, Jer!
>
> http://www.winehq.org/  doesn't work here......

DNS just got updated and the site seems to load up allot faster than before :)

Nice Work Indeed!

[Stefan Leichter]

Am Mittwoch, 31. August 2005 01:30 schrieb Jeremy Newman:
> The webserver is back online. There are still plenty of quirks to fix.
> Feel free to bug me here on wine-devel about any issues that crop up.

Hi Jeremy,

thank you for the new webserver.

Is it possible to get the timestamps back into the mailing list archive? It is  
useful e.g. for regression testing to see when patches were committed to cvs.

Thanks Stefan

[Ron Jensen]

On Fri, Sep 02, 2005 at 11:22:21PM +0200, Stefan Leichter wrote:
> Am Mittwoch, 31. August 2005 01:30 schrieb Jeremy Newman:
> > The webserver is back online. There are still plenty of quirks to fix.
> > Feel free to bug me here on wine-devel about any issues that crop up.
>
> Hi Jeremy,
>
> thank you for the new webserver.
>
> Is it possible to get the timestamps back into the mailing list archive? It is  
> useful e.g. for regression testing to see when patches were committed to cvs.
>
> Thanks Stefan

I was wondering the same thing.  However it looks like this feature doesn't 
(yet) exist in Pipermail.

See:
 http://sourceforge.net/tracker/index.php?func=detail&aid=843141&grou...

Perhaps someone could dig through http://mail.python.org/pipermail/mailman-users/
and see if there is indeed an answer I missed?

The other thing in the archive that has been annoying me is the badly 
out of range dates.  See 
http://www.mail-archive.com/[e-mail]/msg08224.html
for a huge flame war dust-up on this issue.  I'm in the date-munging group, 
or the sort by date means system-received date not sent date.

There is a mailman developer archive here: 
http://www.mail-archive.com/[e-mail]/info.html done by
MHonArc v2.6.15.

Ron

[Ron Jensen]

On Fri, Sep 02, 2005 at 11:22:21PM +0200, Stefan Leichter wrote:
> Am Mittwoch, 31. August 2005 01:30 schrieb Jeremy Newman:
> > The webserver is back online. There are still plenty of quirks to fix.
> > Feel free to bug me here on wine-devel about any issues that crop up.
>
> Hi Jeremy,
>
> thank you for the new webserver.
>
> Is it possible to get the timestamps back into the mailing list archive? It is  
> useful e.g. for regression testing to see when patches were committed to cvs.
>
> Thanks Stefan

I was wondering the same thing.  However it looks like this feature doesn't 
(yet) exist in Pipermail.

See:
 http://sourceforge.net/tracker/index.php?func=detail&aid=843141&grou...

Perhaps someone could dig through http://mail.python.org/pipermail/mailman-users/
and see if there is indeed an answer I missed?

The other thing in the archive that has been annoying me is the badly 
out of range dates.  See 
http://www.mail-archive.com/[e-mail]/msg08224.html
for a huge flame war dust-up on this issue.  I'm in the date-munging group, 
or the sort by date means system-received date not sent date.

There is a mailman developer archive here: 
http://www.mail-archive.com/[e-mail]/info.html done by
MHonArc v2.6.15.

Ron

[Jeremy Newman]

No, it is not possible.

On Fri, 2005-09-02 at 23:22 +0200, Stefan Leichter wrote:
> Am Mittwoch, 31. August 2005 01:30 schrieb Jeremy Newman:
> > The webserver is back online. There are still plenty of quirks to fix.
> > Feel free to bug me here on wine-devel about any issues that crop up.
>
> Hi Jeremy,
>
> thank you for the new webserver.
>
> Is it possible to get the timestamps back into the mailing list archive? It is  
> useful e.g. for regression testing to see when patches were committed to cvs.
>
> Thanks Stefan

[Brian Vincent]

On 9/2/05, Stefan Leichter  wrote:
> Is it possible to get the timestamps back into the mailing list archive? It is
> useful e.g. for regression testing to see when patches were committed to cvs.

Yeah, it's actually a showstopper for me too and I asked the same
thing.  It's exactly why there was no WWN last and why there isn't
likely to be one this week.  I'm sure mailman has some great features,
but for me the pipermail archives suck rocks.

-Brian

[Jeremy Newman]

I'm really sorry you guys feel that way. The complaints have been very
minimal overall. If I wasn't so busy I can spend more time on it. My
problem is that I don't want to go back to Hypermail either. It has
serious issues with security and its attachment handling. So any other
options/suggestions I'll take. Or if anyone has some ideas on how Brian
can get the info he needs.

I found a patch that will add the date to the message lists. Problem is,
this goes against my policies. I don't like to patch binary packages
beyond the normal configuration files. This gets me into a quagmire when
I have to update the packages during a security update.

It does seem very strange that mailman does not have the date built in.
It does let you customize the templates, but leaves out the options for
dates and post counts. The patch I found was from way back in 2003. They
didn't even accept it back then. Makes me scratch my head when a good
open source project like mailman does not accept obvious improvements.

On Tue, 2005-09-06 at 14:36 -0600, Brian Vincent wrote:
> On 9/2/05, Stefan Leichter  wrote:
> > Is it possible to get the timestamps back into the mailing list archive? It is
> > useful e.g. for regression testing to see when patches were committed to cvs.
>
> Yeah, it's actually a showstopper for me too and I asked the same
> thing.  It's exactly why there was no WWN last and why there isn't
> likely to be one this week.  I'm sure mailman has some great features,
> but for me the pipermail archives suck rocks.
>
> -Brian