From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 2.6.1-1
Date: Wed, 21 Dec 2016 20:38:00 -0000 [thread overview]
Message-ID: <20161221203756.GA11372@calimero.vinschen.de> (raw)
In-Reply-To: <6544a6fc-1c2e-a610-7b8c-fd63276c6d7a@tiscali.co.uk>
[-- Attachment #1: Type: text/plain, Size: 2409 bytes --]
On Dec 21 19:10, David Stacey wrote:
> On 18/12/16 08:41, Corinna Vinschen wrote:
> > I uploaded Cygwin to release 2.6.1-1.
> Just a curiosity: the file timestamps for the source and binary are a day
> apart. Normally, both are created and uploaded at the same time. I'm sure
> there's a good reason for this, but just being cautious...
Dunno who touched the date of the source files, they should be the same
date as the binary files. However, only the date is weird, the files are
still intact. For your safety, here are the expected sha512sums:
32 bit:
7f23816d247419ce991a672388d8e1e69ac768992a686d86f2b8550f6b89fc5387d09290ae1b0298d0352af17783c13133326487766925a85bdbc663031b539f cygwin-2.6.1-1-src.tar.xz
81fa22f667661f214281573ae597bdffa071603bfe19ff9d72871fffee722080df22a60f5bcbd60307c718371259570f671671254864afe1449a76c6610bb392 cygwin-2.6.1-1.tar.xz
47ddce4460fd1eafc7e43db9175e409204c0eff48336c3bb8891972113ac60d177e93d728d9c57b2ce6d36d5ac5688451f1455a0f25eb8f57cd870f621c7b17d cygwin-debuginfo/cygwin-debuginfo-2.6.1-1.tar.xz
667e41ae67de8d98d9f53ba09326d34570a766e740fc871f8011773068f71ad71daf11bd185d9efe5725b161c3038ce308c88d5dc59e3efc9bc4127f14a9e7cc cygwin-devel/cygwin-devel-2.6.1-1.tar.xz
b740acccd9b8a44e2b02500050ab459cc03a576860e3e75d9e5388b0c32baf91cda0447220a15f9cadfb68ccd5fe10b574fb3f586bacea7f46afe4652ed4b637 cygwin-doc/cygwin-doc-2.6.1-1.tar.xz
64 bit:
ed36e03fa1bdd1aa57ffa4865c1d110ff9110daed57c0f146b8475127b2cf397c2ac6d3c38f5e7843636a47bc48432937ae7f9392bba20b72babe946f4d4e050 cygwin-2.6.1-1-src.tar.xz
728c6403a4fabbaaa5e1ecc500400323f9107b3116ed2e1ba23ebec60b5c60aa36ffadde1fb50047dbb678a3f30c1e7e956440bd67537a8e887d9fca45cda8b6 cygwin-2.6.1-1.tar.xz
fb32633609966940fc5803db78cea8fa74ca0dec0de4b6b3912a54a262989714a2363cd311f1c766c56c5f528f1ef2f77cf185510295650c992a0ef5788571ab cygwin-debuginfo/cygwin-debuginfo-2.6.1-1.tar.xz
11ece3e3b11c2d673ddaaf94a727c7f0801cd05857e0782c130578fc825e3657727eae3d8272b9874f8ee2c45b318bb15ec3b8ab11bc8cd519eb6ebfe841df6b cygwin-devel/cygwin-devel-2.6.1-1.tar.xz
8445659b9023ff9a3249c7b65cb110e2dbb4f05276672840368e7b6144bcb95f4fa5d476f4a6bf78c0994cc4e4a244a97fd6f61b41c167daf04f23b48a167f11 cygwin-doc/cygwin-doc-2.6.1-1.tar.xz
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-12-21 20:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 8:43 Corinna Vinschen
2016-12-21 19:10 ` David Stacey
2016-12-21 20:38 ` Corinna Vinschen [this message]
2017-01-10 0:39 Steven Penny
2017-01-10 20:08 ` Brian Inglis
2017-01-11 0:00 ` Steven Penny
2017-01-11 6:51 ` Brian Inglis
2017-01-11 12:52 ` Steven Penny
2017-01-11 17:54 ` Brian Inglis
2017-01-11 19:37 ` Steven Penny
2017-01-11 20:41 ` Eliot Moss
2017-01-11 23:19 ` Steven Penny
2017-01-11 23:22 ` Eliot Moss
2017-01-11 23:29 ` Steven Penny
2017-01-11 21:41 ` Brian Inglis
2017-01-11 23:27 ` Steven Penny
2017-01-11 1:35 ` Michael Enright
2017-01-12 14:23 ` John Hein
2017-01-12 18:48 ` David Macek
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=20161221203756.GA11372@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).