From: Kamil Dudka <kdudka@redhat.com>
To: Axel Beckert <abe@deuxchevaux.org>
Cc: zsh-workers@zsh.org
Subject: Re: Will make zsh-5.5.1 this evening
Date: Tue, 17 Apr 2018 13:34:44 +0200 [thread overview]
Message-ID: <1858008.dYFrlKloFp@kdudka-nb> (raw)
In-Reply-To: <20180417111144.GQ28806@sym.noone.org>
On Tuesday, April 17, 2018 1:11:45 PM CEST Axel Beckert wrote:
> Hi,
>
> On Mon, Apr 16, 2018 at 09:35:27AM +0100, Peter Stephenson wrote:
> > say about 1900 BST (UTC+1), unless anyone has anything that needs to go
> > in. But I don't think any more urgent problems have cropped up.
>
> JFTR: I saw the signed tag in git and tar balls on www.zsh.org (and as
> usual no tar ball on sf.net yet),
Where exactly did you look for it?
I was able to download it from sourceforge four hours ago:
https://downloads.sourceforge.net/zsh/zsh-5.5.1.tar.xz
https://downloads.sourceforge.net/zsh/zsh-5.5.1.tar.xz.asc
Kamil
> but yet no other announcement than this pre-announcement.
>
> I've uploaded 5.5.1 to Debian Unstable last night and it builds fine
> so far:
> https://buildd.debian.org/status/package.php?p=zsh&suite=unstable
>
> The dependency issues mentioned on that page are about currently not
> up-to-date texlive packages on all architectures in Debian Unstable
> and can be ignored. Debian Buildds seem to insist on the newest
> version of (some) build-dependencies and hence it's just a matter of
> time until zsh 5.5.1 gets built on these architectures, too.
>
> Kind regards, Axel
next prev parent reply other threads:[~2018-04-17 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180416095850eucas1p148992afc6c2eee0397808364dc49b63b@eucas1p1.samsung.com>
2018-04-16 8:35 ` Peter Stephenson
2018-04-17 11:11 ` Axel Beckert
2018-04-17 11:34 ` Kamil Dudka [this message]
2018-04-17 14:59 ` Axel Beckert
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=1858008.dYFrlKloFp@kdudka-nb \
--to=kdudka@redhat.com \
--cc=abe@deuxchevaux.org \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).