public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Cc: overseers@sourceware.org
Subject: Re: missing poppler and openjpeg packages on mirrors
Date: Thu, 17 Aug 2017 12:25:00 -0000	[thread overview]
Message-ID: <2f2bd0a8-7ea4-5654-e546-770419da985a@gmail.com> (raw)
In-Reply-To: <b9cc1208-949d-f541-884d-8bcd113a296f@redhat.com>

On 8/16/2017 9:46 PM, Eric Blake wrote:
> On 08/16/2017 05:56 PM, Isaac Hanson wrote:
>> It seems that some packages have recently gone missing from many
>> cygwin mirrors.  Specifically, I have noticed all the poppler and
>> openjpeg packages are gone, while still in the setup.ini and
>> dependencies of other packages.
>>
>> setup.exe reports "HTTP status 404 fetching" and lists the URL to the
>> package, for example,
>> "http://cygwin.mirror.constant.com/x86_64/release/poppler/libpoppler66/libpoppler66-0.52.0-1.tar.xz"
>>
>> Any help would be appreciated.
> 
> As posted earlier on the list:
> 

I don't remember such a post on _this_ list.

> sourceware.org is having some fallout from a hardware upgrade (see [1]).
> 
> Some things got restored from backup.  Work is ongoing.
> 
> [1] https://www.sourceware.org/ml/overseers/2017-q3/msg00060.html
> 

Wouldn't it be easier to move the DNS to point sourceware.org to the IP
of sourceware2.org until the mess is fixed?  Once the repair is complete
the DNS can move back to the original IP.

-- 
cyg Simple

--
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:[~2017-08-17 12:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16 22:56 Isaac Hanson
2017-08-17  1:46 ` Eric Blake
2017-08-17 12:25   ` cyg Simple [this message]
2017-08-17 13:40     ` Jon Turney
2017-08-17 13:35   ` Jon Turney
2017-08-17 16:31     ` Brian Inglis
2017-08-17 18:42       ` Jon Turney

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=2f2bd0a8-7ea4-5654-e546-770419da985a@gmail.com \
    --to=cygsimple@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=overseers@sourceware.org \
    /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).