Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

The ticket for ping is still not resolved by the network team. I’ll check to see if they are resolved any tickets related to the rsync. Shree On Apr 24, 2014, at 2:06 PM, Clemens Lang wrote: > Hi > >> Thanks for your patience, I’ll get that squared soon. > > Just as an update, it seems the d

Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

Hi > Thanks for your patience, I’ll get that squared soon. Just as an update, it seems the distfile mirroring is working again as of yesterday night. A few new distfiles popped up with dates similar to 23-Apr-2014 07:38 (example is wireshark 1.10.7) so thank you for that. MacPorts will still n

Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

On 2014-4-25 03:02 , Clemens Lang wrote: > Hi, > >> Alright that gives me something to chew on. Thanks again. > > The Mavericks base buildslave seems fine now, apparently the working > copy was still locked earlier, but a switch to a branch seems to have > fixed that. I'm not so sure about that,

Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

Clemens Thanks for your patience, I’ll get that squared soon. Shree On Apr 24, 2014, at 10:02 AM, Clemens Lang wrote: > Hi, > >> Alright that gives me something to chew on. Thanks again. > > The Mavericks base buildslave seems fine now, apparently the working > copy was still locked earlier,

Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

Hi, > Alright that gives me something to chew on. Thanks again. The Mavericks base buildslave seems fine now, apparently the working copy was still locked earlier, but a switch to a branch seems to have fixed that. Still persisting are - website not being updated from SVN, and - distfile mirro

Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

On Apr 21, 2014, at 18:59, Shreeraj Karulkar wrote: > I seem to be missing the most obvious. I looked extensively for the > post-commit hooks for macports.css and realized that the file on the server > has a date stamp from Apr 2013. You can see it in the log as well —> > https://www.macports.

Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

Alright that gives me something to chew on. Thanks again. Shree Sent from my iPhone > On Apr 21, 2014, at 6:24 PM, Ryan Schmidt wrote: > > >> On Apr 21, 2014, at 18:59, Shreeraj Karulkar wrote: >> >> I seem to be missing the most obvious. I looked extensively for the >> post-commit hooks f

Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

On 2014-4-22 09:59 , Shreeraj Karulkar wrote: > Clemens > I seem to be missing the most obvious. I looked extensively for the > post-commit hooks for macports.css and realized that the file on the server > has a date stamp from Apr 2013. You can see it in the log as well —> > https://www.macport

Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

Clemens I seem to be missing the most obvious. I looked extensively for the post-commit hooks for macports.css and realized that the file on the server has a date stamp from Apr 2013. You can see it in the log as well —> https://www.macports.org/macports.css Can anyone confirm if it has worked

Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

All Just wanted to let you know that I haven’t forgotten about this. On the build base issue, I have tried the same command that has worked on others and also su to buildbot and tried to run from there. Each time I get the expected reply back so it has the new cert but there is still a problem.

Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

Hi, > On 2014-4-21 15:46 , Shreeraj Karulkar wrote: > > [2,3,4] Lion seems to have an non svn error now, Mavericks is still > > building will keep a watch. And Mtn Lion is now okay. > > Yeah, Lion is now failing the trace mode test. That's actually expected at the moment. I cannot look into that

Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

On 2014-4-21 15:46 , Shreeraj Karulkar wrote: > [2,3,4] Lion seems to have an non svn error now, Mavericks is still building > will keep a watch. And Mtn Lion is now okay. Yeah, Lion is now failing the trace mode test. Mavericks seems to be timing out while checking out base, it's like the connec

Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

still persisting >> with >> MacPorts' infrastructure at MacOSForge when you have some time? >> >> First, the MacPorts website isn't being updated from the SVN after a commit. >> This used to happen instantly, so I assume it should be defined somewhere i

Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

On Apr 21, 2014, at 00:46, Shreeraj Karulkar wrote: > [5,6] In the last email chain I had mentioned that the > ../var/macports/software directory was about 24 G when it should’ve been > about 8 to 9 G. But I haven’t heard if I need to delete any files there, if > so which ones? No I think we

Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

hen you have some time? > > First, the MacPorts website isn't being updated from the SVN after a commit. > This used to happen instantly, so I assume it should be defined somewhere in > a post-commit hook. For example, I just committed [1], which should now be > visibl

MacPorts website and distfiles not updating, buildbots don't accept SSL certificate

Hi could you please look into the following issues that are still persisting with MacPorts' infrastructure at MacOSForge when you have some time? First, the MacPorts website isn't being updated from the SVN after a commit. This used to happen instantly, so I assume it should be defined

Re: macports website

On Jul 17, 2009, at 1:27 AM, Ryan Schmidt wrote: On Jul 14, 2009, at 05:58, Jeremy Lavergne wrote: I wonder, what were the advantages of going with XHTML to begin with? I haven't been terribly active in web development in some years, but when I was, XHTML was the new hotness and the reco

Re: macports website

On 2009-07-14 06:58:50 -0400, Jeremy Lavergne wrote: > Future work? I wonder, what were the advantages of going with XHTML > to begin with? One can use XML tools on it. I sometimes do that on the bug database to see if I haven't missed anything and so on. -- Vincent Lefèvre - Web:

Re: macports website

On 2009-07-14 16:13:46 -0400, Kristofer Henriksson wrote: > As a side note, such divergent error handling makes it a shame that > there is no debug-type option for error handling to be set in > browsers, with XHTML-style failure when debugging is enabled and > silent HTML-style perseverance when di

Re: macports website

On Jul 17, 2009, at 01:40, William Siegrist wrote: On Jul 16, 2009, at 11:00 PM, Ryan Schmidt wrote: On Jul 14, 2009, at 09:50, William Siegrist wrote: On Jul 14, 2009, at 7:26 AM, Kristofer Henriksson wrote: It seems that some are simply opposed to XHTML. Is there a particular reason to

Re: macports website

On Jul 16, 2009, at 11:00 PM, Ryan Schmidt wrote: On Jul 14, 2009, at 09:50, William Siegrist wrote: On Jul 14, 2009, at 7:26 AM, Kristofer Henriksson wrote: It seems that some are simply opposed to XHTML. Is there a particular reason to dislike using it for the site? http://webkit.org/

Re: macports website

On Jul 14, 2009, at 09:50, William Siegrist wrote: On Jul 14, 2009, at 7:26 AM, Kristofer Henriksson wrote: It seems that some are simply opposed to XHTML. Is there a particular reason to dislike using it for the site? http://webkit.org/blog/68/understanding-html-xml-and-xhtml/ If you're

Re: macports website

On Jul 14, 2009, at 05:58, Jeremy Lavergne wrote: I wonder, what were the advantages of going with XHTML to begin with? I haven't been terribly active in web development in some years, but when I was, XHTML was the new hotness and the recommended way to code websites. Perhaps Juan had the

Re: macports website

On Jul 14, 2009, at 05:40, Joshua Root wrote: Wanting to support IE is the number one reason to use HTML rather than XHTML. IE has never handled XHTML; if you serve it with the right MIME type it can't display it and just downloads the file, and if you serve it as text/html it parses it as inva

Re: macports website

I read the article he linked to, and it seems that one main concern with XHTML is the MIME type issue, which exists because IE does not deal with the XHTML mime type properly. We deal with this by sending the wrong MIME type to IE. The result is that IE receives invalid markup but parses it anyway

Re: macports website

I don't seeing using HTML 5 as an upgrade so much as a side step. It doesn't break things -- even as far back as IE6, which most companies use. Also, since yet another ticket has shown up due to having to do fun fancy tagging due to the XML side of XHTML, I figured it would be another re

Re: macports website

At 6:31 PM -0400 7/13/09, Jeremy Lavergne wrote: >Interested in this transition, I asked wms how to go about instigating >the change. He directed me to ask you for your thoughts on bringing >the site into HTML 5. So, ticket-filers, hecklers, ... Ah, my category. It's been my experience that eve

Re: macports website

On Jul 14, 2009, at 7:26 AM, Kristofer Henriksson wrote: I believe that while the W3C will be disbanding the XHTML working group, this does not extend to the specification itself, which will exist in the HTML 5 specification (see http://www.w3.org/TR/html5/the-xhtml-syntax.html#the-xhtml-syntax

Re: macports website

I believe that while the W3C will be disbanding the XHTML working group, this does not extend to the specification itself, which will exist in the HTML 5 specification (see http://www.w3.org/TR/html5/the-xhtml-syntax.html#the-xhtml-syntax). In other words, XHTML will continue to be have the same le

Re: macports website

On Jul 14, 2009, at 3:57 AM, Joshua Root wrote: On 2009-7-14 20:50, Jeremy Lavergne wrote: And also getting the site off of XHTML ;-) A move for which you still haven't mentioned any specific advantages. The W3C has abandoned XHTML2, so we should not do any new work in XHTML. I suppose

Re: macports website

Future work? I wonder, what were the advantages of going with XHTML to begin with? On Jul 14, 2009, at 6:57 AM, Joshua Root wrote: A move for which you still haven't mentioned any specific advantages. smime.p7s Description: S/MIME cryptographic signature _

Re: macports website

On 2009-7-14 20:50, Jeremy Lavergne wrote: > And also getting the site off of XHTML ;-) A move for which you still haven't mentioned any specific advantages. - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.

Re: macports website

On Jul 14, 2009, at 6:40 AM, Joshua Root wrote: On 2009-7-14 08:31, Jeremy Lavergne wrote: I'd like to point out that using XHTML was a somewhat divergent path from HTML. With the advent of HTML 5, we find ourselves once again returning to the HTML side of things. On the other hand: XHTML5.

Re: macports website

On 2009-7-14 08:31, Jeremy Lavergne wrote: > I'd like to point out that using XHTML was a somewhat divergent path > from HTML. With the advent of HTML 5, we find ourselves once again > returning to the HTML side of things. On the other hand: XHTML5. > Interested in this transition, I asked wms h

Re: macports website

I'd suggest using the HTML 5 doctype so it's ready to go in the future, but essentially using HTML 4.01 transitional. On Jul 14, 2009, at 2:39 AM, Ryan Schmidt wrote: I have not kept up with the developments of HTML 5 except for the canvas tag. Is there a specific feature of HTML 5 you belie

Re: macports website

On Jul 13, 2009, at 17:31, Jeremy Lavergne wrote: We've had a ticket (#20278) come in about the web site once again. Previously, to our chagrin the XHTML broke in IE7 (#14062). I'd like to point out that using XHTML was a somewhat divergent path from HTML. With the advent of HTML 5, we f

macports website

We've had a ticket (#20278) come in about the web site once again. Previously, to our chagrin the XHTML broke in IE7 (#14062). I'd like to point out that using XHTML was a somewhat divergent path from HTML. With the advent of HTML 5, we find ourselves once again returning to the HTML side

Re: MacPorts website scheduled downtime Friday morning

On Oct 12, 2007, at 8:54 AM, James Berry wrote: On Oct 10, 2007, at 9:00 PM, James Berry wrote: The MacPorts web presence may be down for a (hopefully shor)t period of time on Friday morning, about 9:00 am US/Pacific. The MacPorts site will go down shortly, and will hopefully be down for

Re: MacPorts website scheduled downtime Friday morning

On Oct 10, 2007, at 9:00 PM, James Berry wrote: The MacPorts web presence may be down for a (hopefully shor)t period of time on Friday morning, about 9:00 am US/Pacific. The MacPorts site will go down shortly, and will hopefully be down for less than 1/2 hour. James The macosforge tea

Re: MacPorts website scheduled downtime Friday morning

The migration should not affect the rsync server. Sent from my iPhone On Oct 11, 2007, at 4:09 AM, Blair Zajac <[EMAIL PROTECTED]> wrote: James Berry wrote: The MacPorts web presence may be down for a (hopefully shor)t period of time on Friday morning, about 9:00 am US/Pacific. The macosforg

Re: MacPorts website scheduled downtime Friday morning

James Berry wrote: The MacPorts web presence may be down for a (hopefully shor)t period of time on Friday morning, about 9:00 am US/Pacific. The macosforge team is moving the web server that serves MacPorts to a new machine and ip address, and it may take DNS a little while to settle across t

MacPorts website scheduled downtime Friday morning

The MacPorts web presence may be down for a (hopefully shor)t period of time on Friday morning, about 9:00 am US/Pacific. The macosforge team is moving the web server that serves MacPorts to a new machine and ip address, and it may take DNS a little while to settle across the move. (DNS TTL