<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:wfw="http://wellformedweb.org/CommentAPI/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
>
<!-- MHonArc v2.6.10 -->
	<channel>
		<title>cross-project-issues-dev</title>
		<link>http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/maillist.html</link>
		<description>cross-project-issues-dev</description>
		<language>en-us</language>
		<pubDate>Thu, 22 Oct 2009 18:10:16 GMT</pubDate>
		<lastBuildDate>Thu, 22 Oct 2009 18:10:16 GMT</lastBuildDate>
		<docs>http://blogs.law.harvard.edu/tech/rss</docs>
		<generator>MHonArc RSS 2.0 RCFile</generator>
		<managingEditor>webmaster@eclipse.org (Webmaster)</managingEditor>
		<webMaster>webmaster@eclipse.org (Webmaster)</webMaster>
		<image>
			<title>cross-project-issues-dev</title>
			<url>http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg</url>
			<link>http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/maillist.html</link>
		</image>
 

	<item>
		<title>Re: [cross-project-issues-dev] Permissions problems on	download.eclipse.org</title>
		<link>http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03726.html</link>
		<description> an eye open. I'd say if you hear no objections by, say, next Wednesday morning, now would be a good time to do it ... no widespread pending releases or other sensitive timing that I know of. Done.  You're now all responsible for ensuring the permissions a...</description>
		<content:encoded><![CDATA[<table width="100%"><tr><td bgcolor="#ffffff" style="background-color: #ffffff; color: #000000; "><font color="#000000">



On 10/22/2009 01:45 PM, David M Williams wrote:
<blockquote
 cite=""
 type="cite">
  <blockquote type="cite">
    <pre wrap="">With that in mind, I'd rather just turn it off and tell everyone to keep 
    </pre>
  </blockquote>
  <pre wrap="">an eye open.

I'd say if you hear no objections by, say, next Wednesday morning, now 
would be a good time to do it ... no widespread pending releases or other 
sensitive timing that I know of. 
  </pre>
</blockquote>
<small>Done.&nbsp; You're now all responsible for ensuring the permissions
are correct on your downloads folders.</small><br>
<blockquote
 cite=""
 type="cite">
  <pre wrap="">Is there a wiki yet for "how to put code on eclipse download server". 
Maybe that should be updated or if not one yet ... any volunteers? 
  </pre>
</blockquote>
<small><a class="moz-txt-link-freetext" href="http://wiki.eclipse.org/IT_Infrastructure_Doc">http://wiki.eclipse.org/IT_Infrastructure_Doc</a></small><br>
<br>
<small>There is already a blurb for permissions, but it would be nice
if someone else were to review all those words to make sure they make
sense<small>.</small>&nbsp; In my mind, it's all perfectly clear.</small><br>


</font></td></tr></table>]]></content:encoded>
		<pubDate>Thu, 22 Oct 2009 18:00:57 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03726.html</guid>
		<author>denis.roy@xxxxxxx (Denis Roy)</author>
	</item>
	<item>
		<title>Re: [cross-project-issues-dev]	Permissions	problems	on	download.eclipse.org</title>
		<link>http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03725.html</link>
		<description> an eye open. I'd say if you hear no objections by, say, next Wednesday morning, now would be a good time to do it ... no widespread pending releases or other sensitive timing that I know of. In the mean time, if any &amp;quot;release engineers&amp;quot; don't know what we ...</description>
		<content:encoded><![CDATA[<pre>&gt; With that in mind, I'd rather just turn it off and tell everyone to keep 
an eye open.

I'd say if you hear no objections by, say, next Wednesday morning, now 
would be a good time to do it ... no widespread pending releases or other 
sensitive timing that I know of. 

In the mean time, if any &quot;release engineers&quot; don't know what we are 
talking about, better ask now! :) 

Is there a wiki yet for &quot;how to put code on eclipse download server&quot;. 
Maybe that should be updated or if not one yet ... any volunteers? 



</pre>]]></content:encoded>
		<pubDate>Thu, 22 Oct 2009 17:45:47 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03725.html</guid>
		<author>david_williams@xxxxxxx (David M Williams)</author>
	</item>
	<item>
		<title>Re: [cross-project-issues-dev] Permissions	problems	on	download.eclipse.org</title>
		<link>http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03724.html</link>
		<description> You know, not a day goes by where I don't ask myself that same question! On some days, that is practically the case.  It's currently set up to run only twice a day, and that's only when it is allowed to run.  Heavy server load often causes this job to be ...</description>
		<content:encoded><![CDATA[<table width="100%"><tr><td bgcolor="#ffffff" style="background-color: #ffffff; color: #000000; "><font color="#000000">



On 10/21/2009 11:39 PM, David M Williams wrote:
<blockquote
 cite=""
 type="cite">
  <pre wrap="">I wonder ... Are you being too helpful? 
  </pre>
</blockquote>
<small><br>
You know, not a day goes by where I don't ask myself that same question!<br>
<br>
</small><br>
<blockquote
 cite=""
 type="cite">
  <pre wrap="">What if the fix-permissions script never ran, and we slowly
transitioned to expecting everyone to do it right from the
beginning.
  </pre>
</blockquote>
<small><br>
On some days, that is practically the case.&nbsp; It's currently set up to
run only twice a day, and that's only when it is allowed to run.&nbsp; Heavy
server load often causes this job to be paused or terminated.&nbsp; We've
seen previously some cases where it hadn't run in days.<br>
<br>
With that in mind, I'd rather just turn it off and tell everyone to
keep an eye open.<br>
<br>
Denis<br>
</small><br>
<br>
<br>


</font></td></tr></table>]]></content:encoded>
		<pubDate>Thu, 22 Oct 2009 17:21:37 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03724.html</guid>
		<author>denis.roy@xxxxxxx (Denis Roy)</author>
	</item>


	<item>
		<title>Re: [cross-project-issues-dev] Permissions problems	on	download.eclipse.org</title>
		<link>http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03723.html</link>
		<description>I wonder ... Are you being too helpful? What if the fix-permissions script never ran, and we slowly transitioned to expecting everyone to do it right from the beginning. As it is, someone may be uploading it &amp;quot;wrong&amp;quot;, its auto-fixed for them, and this works...</description>
		<content:encoded><![CDATA[<pre>I wonder ... Are you being too helpful? 

What if the fix-permissions script never ran, and we slowly
transitioned to expecting everyone to do it right from the
beginning.

As it is, someone may be uploading it &quot;wrong&quot;, its auto-fixed for
them, and this works fine for a long long time, they don't even
realize its not done right, but instead cleaned up for them, but
then when once not auto-fixed (due to server overload) that is when
the &quot;problem suddenly appears&quot; ... and the releng teams shout &quot;we
didn't change a thing, and it used to work just fine, what changed
in the infrastructure&quot;. And by the time the shouting has died down,
and the explanations given, several hundred gigabytes have been
wasted copying, deleting, and then copying again full directories
to the 70 mirrors.

But, by then, everything is working again, so (some) teams decide
since its not raining right now that they will fix the roof later.

This could be &quot;rolled out&quot; slowly, so first, say, webtools wouldn't
be auto-fixed up, then we (yes, you and me) would work to inspect
things, make sure I'm setting thing right, etc. And then move on
.... to modeling? Or who ever.

This, or similar plan, would &quot;force&quot; teams to code things correctly
(and set their umask bits correctly, which I'm now an expert on (ha
ha)). I would seem to end up in a better infrastructure in several
months (and then stay that way over the years as we grow to 10
million files! :)
 
Naturally, you could still be helpful on request, both in education
and if someone &quot;messed up&quot; (or, just give them a safe script to run
for &quot;post fix-up&quot;). Perhaps the &quot;auto-fix-permissions&quot; script could
be changed as a sort of &quot;audit&quot; tool (and would not have to run
very often at all to spot teams not doing it correctly).

There's probably even other rsync &quot;tips&quot; we should codify ... such
as do NOT use -t when rsyncing to 'downloads'! As &quot;smart&quot; as that
sometimes is, it is contradicted by our mirroring system ... since
&quot;old&quot; files will &quot;appear&quot; to have been there the last time a mirror
synched up, but won't be, so users get 404 errors from mirrors ...
and I didn't learn that until just this year!

What do you think? 









From:
&quot;Eclipse Webmaster (Denis Roy)&quot; &lt;webmaster@xxxxxxxxxxx&gt;
To:
Cross project issues &lt;cross-project-issues-dev@xxxxxxxxxxx&gt;
Date:
10/19/2009 09:35 AM
Subject:
[cross-project-issues-dev] Permissions problems on download.eclipse.org
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx



Greetings, 

We've been getting complaints [1] from our mirror sites that many 
Permission Denied errors are occurring when syncing with 
download.eclipse.org.  When you upload your files, please ensure that they 
are world-readable (rw-rw-r), and that directories are world-readable and 
executable (rwxrwxr-x).

If you use RSYNC, you can simply set your permissions correctly prior to 
rsync, and use the -p option with rsync.  Please note that it is not 
acceptable to remove file permissions to 'hide' content on 
download.eclipse.org. If it's there, it should be open to all.

We have automated scripts to fix such anomalies, but since 
download.eclipse.org now has over 1 million files, these scripts cannot 
run as often as they used to.

Thanks for your help!

Denis


[1] <a  href="http://dev.eclipse.org/mhonarc/lists/eclipse-mirrors/msg00496.html">http://dev.eclipse.org/mhonarc/lists/eclipse-mirrors/msg00496.html</a>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
<a  href="https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev">https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev</a>




</pre>]]></content:encoded>
		<pubDate>Thu, 22 Oct 2009 03:39:33 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03723.html</guid>
		<author>david_williams@xxxxxxx (David M Williams)</author>
	</item>
	<item>
		<title>Re: [cross-project-issues-dev] Nightly builds - naming schemes</title>
		<link>http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03722.html</link>
		<description> Doesn't this pattern exclude the once-a-week I builds and M builds as well? PW Yup </description>
		<content:encoded><![CDATA[<table width="100%"><tr><td bgcolor="#ffffff" style="background-color: #ffffff; color: #000000; "><font color="#000000">



On 10/21/2009 09:29 AM, Paul Webster wrote:
<blockquote
 cite=""
 type="cite">
  <pre wrap="">On Wed, Oct 21, 2009 at 9:25 AM, Denis Roy <a class="moz-txt-link-rfc2396E" href="mailto:denis.roy@xxxxxxxxxxx">&lt;denis.roy@xxxxxxxxxxx&gt;</a> wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">
drops/I*
drops/M*
    </pre>
  </blockquote>
  <pre wrap="">
Doesn't this pattern exclude the once-a-week I builds and M builds as well?

PW

  </pre>
</blockquote>
<small>Yup</small><br>


</font></td></tr></table>]]></content:encoded>
		<pubDate>Wed, 21 Oct 2009 13:31:20 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03722.html</guid>
		<author>denis.roy@xxxxxxx (Denis Roy)</author>
	</item>
	<item>
		<title>Re: [cross-project-issues-dev] Nightly builds - naming schemes</title>
		<link>http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03721.html</link>
		<description> Doesn't this pattern exclude the once-a-week I builds and M builds as well? PW </description>
		<content:encoded><![CDATA[<pre>On Wed, Oct 21, 2009 at 9:25 AM, Denis Roy &lt;denis.roy@xxxxxxxxxxx&gt; wrote:
&gt;
&gt; drops/I*
&gt; drops/M*

Doesn't this pattern exclude the once-a-week I builds and M builds as well?

PW


-- 
Paul Webster
Hi floor.  Make me a sammich! - GIR

</pre>]]></content:encoded>
		<pubDate>Wed, 21 Oct 2009 13:29:14 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03721.html</guid>
		<author>pwebster@xxxxxxx (Paul Webster)</author>
	</item>
	<item>
		<title>[cross-project-issues-dev] Nightly builds - naming schemes</title>
		<link>http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03720.html</link>
		<description> Greetings, We try to avoid replicating Nightly builds to our mirrors, since they are short-lived and generate few downloads*.  To do this, we have an exclusion list based on a specific set of directory patterns.  Below is the current list...p; If you are ...</description>
		<content:encoded><![CDATA[<table width="100%"><tr><td bgcolor="#ffffff" style="background-color: #ffffff; color: #000000; "><font color="#000000">



<font size="-1">Greetings,<br>
<br>
We try to avoid replicating Nightly builds to our mirrors, since they
are short-lived and generate few downloads*.&nbsp; To do this, we have an
exclusion list based on a specific set of directory patterns.&nbsp; Below is
the current list...&nbsp; If you are producing Nightly builds, please ensure
that the directory naming scheme matches one of the excluded patterns
below, or let us know what your pattern is.&nbsp; Our mirrors will thank you.<br>
<br>
drops/I*<br>
drops/N*<br>
drops/M*<br>
webtools/committers/<br>
callisto/staging/ <br>
callisto/testUpdates/ <br>
eclipse/testUpdates/ <br>
eclipse/updates/3.2milestones <br>
dev/TPTP* <br>
tools/cdt/builds/* <br>
modeling/gmf/downloads/drops/B* <br>
*drops/*/N* <br>
*drops/*/I*<br>
<br>
Thanks,<br>
<br>
Denis<br>
<br>
* We do replicate _everything_ to our Amazon mirror so that you can
still get speedy downloads for excluded files.<br>
</font>
<div class="moz-signature"><br>
</div>


</font></td></tr></table>]]></content:encoded>
		<pubDate>Wed, 21 Oct 2009 13:25:22 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03720.html</guid>
		<author>denis.roy@xxxxxxx (Denis Roy)</author>
	</item>


	<item>
		<title>Re: [cross-project-issues-dev] p2 API changes in Helios</title>
		<link>http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03719.html</link>
		<description> </description>
		<content:encoded><![CDATA[
<p>Hi Eric,<br>
<br>
The command line tools will not be affected.<br>
If they were, I would send a note on the cross-project ML.<br>
<br>
PaScaL<br>
<br>
<img width="16" height="16" src="" border="0" alt="Inactive hide details for Eric Gwin ---10/19/2009 02:30:19 PM---Pascal,"><font color="#424282">Eric Gwin ---10/19/2009 02:30:19 PM---Pascal,</font><br>
<br>

<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="1%"><img width="96" height="1" src="" border="0" alt=""><br>
<font size="2" color="#5F5F5F">From:</font></td><td width="100%"><img width="1" height="1" src="" border="0" alt=""><br>
<font size="2">Eric Gwin &lt;eric.gwin@xxxxxxxxxx&gt;</font></td></tr>

<tr valign="top"><td width="1%"><img width="96" height="1" src="" border="0" alt=""><br>
<font size="2" color="#5F5F5F">To:</font></td><td width="100%"><img width="1" height="1" src="" border="0" alt=""><br>
<font size="2">Pascal Rapicault/Ottawa/IBM@IBMCA</font></td></tr>

<tr valign="top"><td width="1%"><img width="96" height="1" src="" border="0" alt=""><br>
<font size="2" color="#5F5F5F">Cc:</font></td><td width="100%" valign="middle"><img width="1" height="1" src="" border="0" alt=""><br>
<font size="2">Cross project issues &lt;cross-project-issues-dev@xxxxxxxxxxx&gt;</font></td></tr>

<tr valign="top"><td width="1%"><img width="96" height="1" src="" border="0" alt=""><br>
<font size="2" color="#5F5F5F">Date:</font></td><td width="100%"><img width="1" height="1" src="" border="0" alt=""><br>
<font size="2">10/19/2009 02:30 PM</font></td></tr>

<tr valign="top"><td width="1%"><img width="96" height="1" src="" border="0" alt=""><br>
<font size="2" color="#5F5F5F">Subject:</font></td><td width="100%"><img width="1" height="1" src="" border="0" alt=""><br>
<font size="2">Re: [cross-project-issues-dev] p2 API changes in Helios</font></td></tr>
</table>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<tt>Pascal,<br>
<br>
I just want to clarify before I open a bug. Our build (ant <br>
command-line), utilizes the p2 tools directly. So I'm potentially <br>
affected by changes, but do not directly call upon the API. If the <br>
command-line interface will remain unchanged I'm likely unaffected.<br>
<br>
Do you still want me open a bug?<br>
<br>
-Eric<br>
<br>
Pascal Rapicault wrote:<br>
&gt;<br>
&gt; If you are a user of the p2 API, please make sure to open a bug <br>
&gt; against p2 as indicated in<br>
&gt; </tt><tt><a href="http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03703.html">http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03703.html</a></tt><tt><br>
&gt;<br>
&gt; Thx<br>
&gt;<br>
&gt; PaScaL<br>
&gt;<br>
&gt; ------------------------------------------------------------------------<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; cross-project-issues-dev mailing list<br>
&gt; cross-project-issues-dev@xxxxxxxxxxx<br>
&gt; </tt><tt><a href="https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev">https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev</a></tt><tt><br>
&gt; &nbsp; <br>
</tt><br>
<br>

<p><a href="gifcUQ08MqfoT.gif" ><img src="gifcUQ08MqfoT.gif" alt="GIF image"></a></p>
<p><a href="gifXqBBXyoqEk.gif" ><img src="gifXqBBXyoqEk.gif" alt="GIF image"></a></p>
]]></content:encoded>
		<pubDate>Mon, 19 Oct 2009 20:31:19 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03719.html</guid>
		<author>Pascal_Rapicault@xxxxxxx (Pascal Rapicault)</author>
	</item>
	<item>
		<title>Re: [cross-project-issues-dev] p2 API changes in Helios</title>
		<link>http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03718.html</link>
		<description> </description>
		<content:encoded><![CDATA[<pre style="margin: 0em;">Pascal,</pre><br>
<tt>I just want to clarify before I open a bug. Our build (ant 
command-line), utilizes the p2 tools directly. So I'm potentially 
affected by changes, but do not directly call upon the API. If the 
command-line interface will remain unchanged I'm likely unaffected.</tt><br>
<br>
<pre style="margin: 0em;">Do you still want me open a bug?</pre><br>
<pre style="margin: 0em;">-Eric</pre><br>
<tt>Pascal Rapicault wrote:
</tt><blockquote style="border-left: #5555EE solid 0.2em; margin: 0em; padding-left: 0.85em"><tt><br>If you are a user of the p2 API, please make sure to open a bug 
against p2 as indicated in<br>
<a  href="http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03703.html">http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03703.html</a></tt><br>
<br>
<pre style="margin: 0em;">Thx</pre><br>
<pre style="margin: 0em;">PaScaL</pre><br>
<pre style="margin: 0em;">------------------------------------------------------------------------</pre><br>
<tt>_______________________________________________<br>
cross-project-issues-dev mailing list<br>
cross-project-issues-dev@xxxxxxxxxxx<br>
<a  href="https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev">https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev</a><br>
  
</tt></blockquote><br>
]]></content:encoded>
		<pubDate>Mon, 19 Oct 2009 18:29:53 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03718.html</guid>
		<author>eric.gwin@xxxxxxx (Eric Gwin)</author>
	</item>
	<item>
		<title>[cross-project-issues-dev] p2 API changes in Helios</title>
		<link>http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03717.html</link>
		<description> If you are a user of the p2 API, please make sure to open a bug against p2 as indicated in http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03703.html Thx PaScaL</description>
		<content:encoded><![CDATA[
<p>If you are a user of the p2 API, please make sure to open a bug against p2 as indicated in<br>
<a href="http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03703.html">http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03703.html</a><br>
<br>
Thx<br>
<br>
PaScaL]]></content:encoded>
		<pubDate>Mon, 19 Oct 2009 17:45:22 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg03717.html</guid>
		<author>Pascal_Rapicault@xxxxxxx (Pascal Rapicault)</author>
	</item>

 
	</channel>
	</rss>
<!-- MHonArc v2.6.10 -->
