From: Jeffrey Walton <noloader@gmail.com>
To: cygwin@cygwin.com
Subject: Re: bzip.org
Date: Fri, 21 Sep 2018 17:01:00 -0000 [thread overview]
Message-ID: <CAH8yC8nez8xViC41nFifEpqvvRJJD8QGxCTVNuhJv3c3Q_T3ww@mail.gmail.com> (raw)
In-Reply-To: <7388bcc5-3d30-f04d-d268-09b1f99c8b27@gmail.com>
On Fri, Sep 21, 2018 at 11:33 AM, cyg Simple <cygsimple@gmail.com> wrote:
> Sadly our beloved http://www.bzip.org has hit the bit bucket. Does
> anyone know where upstream support for bzip2 went?
From https://sourceforge.net/p/valgrind/mailman/message/36403434/ :
> Unfortunately the bzip.org domain is no longer available to the
> bzip2 project. The plan is to move back to sourceware:
> https://sourceware.org/bzip2/
> https://sourceware.org/pub/bzip2/
Jeff
--
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
next prev parent reply other threads:[~2018-09-21 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 15:33 bzip.org cyg Simple
2018-09-21 16:04 ` bzip.org Marco Atzeri
2018-09-21 17:01 ` Jeffrey Walton [this message]
2018-09-21 17:28 ` bzip.org cyg Simple
2018-09-21 21:59 ` bzip.org Henry S. Thompson
2018-09-23 4:28 ` bzip.org cyg Simple
2018-09-23 8:56 ` bzip.org Marco Atzeri
[not found] ` <OF0F781EF9.241BA286-ONC1258311.002D468D-C1258311.002D5A27@onevision.com>
2018-09-24 13:17 ` bzip.org cyg Simple
2018-09-24 21:42 ` bzip.org Jeffrey Walton
2018-10-01 20:51 ` bzip.org Keith Christian
2018-10-01 23:23 ` bzip.org cyg Simple
2018-10-02 16:05 ` bzip.org Keith Christian
2018-11-05 19:17 ` bzip.org cyg Simple
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=CAH8yC8nez8xViC41nFifEpqvvRJJD8QGxCTVNuhJv3c3Q_T3ww@mail.gmail.com \
--to=noloader@gmail.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).