public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jari Aalto <jari.aalto@cante.net>
To: cygwin-apps@cygwin.com
Subject: RFU: mercurial, pngcrush, python-paramiko (was: Re: HEADSUP: Security updates outstanding)
Date: Wed, 20 Aug 2008 11:53:00 -0000	[thread overview]
Message-ID: <87zln7dhuq.fsf@jondo.cante.net> (raw)
In-Reply-To: <48A8C9B4.7010905@users.sourceforge.net> (Yaakov's message of 	"Sun, 17 Aug 2008 20:00:36 -0500")

"Yaakov (Cygwin Ports)"
<yselkowitz-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org> writes:

> Before packagers start focusing on 1.7, it appears that we still have
> a number of security updates required for the 1.5 tree:
>
> By maintainer
> =============
>
> Jari Aalto: mercurial, pngcrush, python-paramiko

FYI, my capacity to participate is severily restrained for the rest of
the year because thunderstorm wiped out all my home network (several
servers, hard disks etc.)

I managed to pull old copies from cygwin.com and upgrade these. Please
upload.

Jari

wget \
    http://cante.net/~jaalto/tmp/cygwin/mercurial/mercurial-1.0.2-1-cygwin.patch \
    http://cante.net/~jaalto/tmp/cygwin/mercurial/mercurial-1.0.2-1.sh \
    http://cante.net/~jaalto/tmp/cygwin/mercurial/mercurial-1.0.2-1-src.tar.bz2 \
    http://cante.net/~jaalto/tmp/cygwin/mercurial/mercurial-1.0.2-1.tar.bz2 \
    http://cante.net/~jaalto/tmp/cygwin/mercurial/mercurial-1.0.2.tar.gz \
    http://cante.net/~jaalto/tmp/cygwin/mercurial/setup.hint

wget \
    http://cante.net/~jaalto/tmp/cygwin/pngcrush/pngcrush-1.6.7-1-cygwin.patch \
    http://cante.net/~jaalto/tmp/cygwin/pngcrush/pngcrush-1.6.7-1.sh \
    http://cante.net/~jaalto/tmp/cygwin/pngcrush/pngcrush-1.6.7-1-src.tar.bz2 \
    http://cante.net/~jaalto/tmp/cygwin/pngcrush/pngcrush-1.6.7-1.tar.bz2 \
    http://cante.net/~jaalto/tmp/cygwin/pngcrush/pngcrush_1.6.7.orig.tar.gz \
    http://cante.net/~jaalto/tmp/cygwin/pngcrush/setup.hint

wget \
    http://cante.net/~jaalto/tmp/cygwin/python-paramiko/python-paramiko-1.7.4-1-cygwin.patch \
    http://cante.net/~jaalto/tmp/cygwin/python-paramiko/python-paramiko-1.7.4-1.sh \
    http://cante.net/~jaalto/tmp/cygwin/python-paramiko/python-paramiko-1.7.4-1-src.tar.bz2 \
    http://cante.net/~jaalto/tmp/cygwin/python-paramiko/python-paramiko-1.7.4-1.tar.bz2 \
    http://cante.net/~jaalto/tmp/cygwin/python-paramiko/python-paramiko-1.7.4.tar.gz \
    http://cante.net/~jaalto/tmp/cygwin/python-paramiko/setup.hint

  parent reply	other threads:[~2008-08-20 11:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18  1:01 HEADSUP: Security updates outstanding Yaakov (Cygwin Ports)
2008-08-18  1:09 ` Christopher Faylor
2008-08-18  2:42   ` Yaakov (Cygwin Ports)
2008-08-18 13:10     ` Christopher Faylor
2008-08-18 13:26       ` Corinna Vinschen
2008-08-18 19:09         ` Yaakov (Cygwin Ports)
2008-08-19  9:56           ` Corinna Vinschen
2008-08-18  3:46 ` David Rothenberger
2008-08-18  6:47 ` Reini Urban
2008-08-18  6:59   ` Reini Urban
2008-08-20 11:53 ` Jari Aalto [this message]
2008-08-20 12:08   ` RFU: mercurial, pngcrush, python-paramiko (was: Re: HEADSUP: Security updates outstanding) Corinna Vinschen
2008-08-20 12:35     ` RFU: mercurial, pngcrush, python-paramiko Jari Aalto
2008-08-20 13:07       ` Corinna Vinschen

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=87zln7dhuq.fsf@jondo.cante.net \
    --to=jari.aalto@cante.net \
    --cc=cygwin-apps@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).