X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=1.4 required=5.0	tests=AWL,BAYES_50,BOTNET,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Message-id: <50718F79.6090101@verizon.net>
Date: Sun, 07 Oct 2012 10:19:37 -0400
From: Charles <millarc@verizon.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-version: 1.0
To: cygwin@cygwin.com
Subject: Re: gnome and hicolor exit code 127 for /usr/bin .vs. /bin
References: <20120929193527.M64303@ds.net> <5067C99F.60108@gmail.com> <20120930131238.M10095@ds.net> <20121001120725.M34953@ds.net> <20121001142414.M8007@ds.net> <20121003111101.M13208@ds.net> <972EEFF84AA34684A3A02402217705B5@ncc1701> <50703D58.5090402@gmail.com> <50705223.4060703@verizon.net> <5070580B.3070306@gmail.com> <50705C0C.2030608@verizon.net> <50708DB4.2020502@gmail.com>
In-reply-to: <50708DB4.2020502@gmail.com>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

Marco

On 10/6/2012 3:59 PM, marco atzeri wrote:
> On 10/6/2012 6:27 PM, Charles wrote:
>
> Charles,
>
> first: do not TOP post
> http://www.idallen.com/topposting.html
>
> it is really annoying.
>
>> Marco,
>>
>> I'm not trying to hijack the thread, Please read Brian's October 5, 2012
>> message. Half way through he raises the corrupt perl man pages issue -
>> only it occured at the GA Tech site.
>
> if you prefer, you drifted to an unrelated issue:
> "corrupt perl man" has no relevance with
> "gnome and hicolor exit code 127"
>
> in the first case the package file is damaged, in the second case
> the setup post-installation script is not working as expected.
>
>>
>> In my original message I requested that it be redirected or that someone
>> tell me the proper procedure.
>>
>> I wasn't sure it there may have been a problem that went beyond VA
>> Tech's site.
>>
>> Also, I checked the Cygwin "Reporting Problems" web site and found no
>> mention about contacting mirror site maintainers. Rather the
>> instructions state "If you can't determine if you've discovered a bug .
>> . . send a detailed description . . . to the appropriate mailoing list."
>>
>> Perhaps the "Reporting Problems" needs to be more clear on this.
>>
>> Charlie
>
> More or less this should belong to the Internet FAQ.
>
> Mirror (for most software) are provided by third party not related
> to original developers. They usually mirrors a lot of different
> software and the content is not controlled by the original site.
>
> On the page
> http://mirror.cs.vt.edu/
>
> you will find their contact information, and also the note :
> "We have begun mirroring the Cygwin Project"
>
> So it is likely they have some initial glitch.
>
>
> Regards
> Marco
>

First - thank you for the bringing the netiquette breach  to my attention.

Second - I thought that Brian Wilson raised the corrupted perl_manpages 
because there was a possibility that those corrupted pages were somehow 
relevant to "gnome and hicolor exit code 127". I therefore inartfully 
"reposted" my October 1 message concerning the Virginia Tech mirror that 
had the same corrupted perl_manpages problem earlier in the week.  I had 
absolutely no idea whether "gnome and hicolor"  and "corrupted 
perl_manpages" were related, but just wanted to point out the VA problem 
just in case they are.

Third - I obviously did not search the correct Virginia Tech site. I 
found the Computer Science Dept. site, but not the mirror site.

Thank you for your patience and lessons.

Regards,
Charlie

--
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

