public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Packages not found by setup 2.873
Date: Fri, 01 Apr 2016 01:09:00 -0000	[thread overview]
Message-ID: <041615D1-AC1D-4176-A371-E42E9D604BE3@etr-usa.com> (raw)
In-Reply-To: <2122944854.25647274.1459414666407.JavaMail.zimbra@partnre.com>

On Mar 31, 2016, at 2:57 AM, EMMANUELLE FOURNIER <emmanuelle.fournier@partnre.com> wrote:
> 
> I've changed in tar.bz2, because in the x86 version of program, they were in tar.bz2.

You’ve misdiagnosed the cause of the change.  Cygwin changed from distributing bz2-packed tarballs to xz-packed tarballs many months ago for both x86 and x86_64.

> But if you mean that is not a cause, I will modify this.

I’d want better proof than what you’ve provided to decide that xz is causing your problems.

> - I've modified setup in order to find packages in tar.bz2 instead of tar.xz.
> 
> - There were errors for each packages, a pop-up came each time with the following message  : "Can't open (null) for readind : no such file”

Try your setup with a fresh set of .xz packages and an unmodified setup.exe binary, downloaded from cygwin.com.  Then if that fails, get back to us.

> 2016/03/25 16:21:28 Selected local directory: C:\D3IPARAM\setup_cygwin\cygwin-setup\http%3a%2f%2fcygwin.gicm.net%3a8080%2f

It seems you’re using bogus domain names in your setup.ini file.  http://cygwin.gicm.net doesn’t resolve:

  http://downforeveryoneorjustme.com/cygwin.gicm.net

I don’t know if this is the primary problem or just a contributing error, but you shouldn’t have setup.exe chasing after things that don’t exist.  At best, it will cause it to do a bunch of work with no useful effect.

> And I can try without "-C base”.

I verified that guess after I posted it: -C base is indeed not necessary.

> A final information : I've made it with x86 setup on x64 target machine. Is it a problem ? I don't think so, but I still wonder.

If you mean that you’re installing 32-bit Cygwin on a 64-bit machine, that’s fine.  The other direction is not fine.


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

  reply	other threads:[~2016-04-01  1:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30  6:27 EMMANUELLE FOURNIER
2016-03-30 17:29 ` Warren Young
2016-03-31  8:58   ` EMMANUELLE FOURNIER
2016-04-01  1:09     ` Warren Young [this message]
2016-04-04  7:45       ` EMMANUELLE FOURNIER
2016-04-04  9:31         ` Achim Gratz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=041615D1-AC1D-4176-A371-E42E9D604BE3@etr-usa.com \
    --to=wyml@etr-usa.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).