From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: dana <dana@dana.is>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Posted zsh 5.9
Date: Sat, 14 May 2022 23:26:05 +0000 [thread overview]
Message-ID: <20220514232605.GB13240@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <734c6a79-86c8-4e29-9f4e-6c2267626390@www.fastmail.com>
dana wrote on Sat, May 14, 2022 at 17:27:26 -0500:
> On Sat 14 May 2022, at 16:50, Daniel Shahaf wrote:
> > For zsh.org there's little question where to put the keyring file, as
> > there's only one relevant directory. Any reason not to upload
> > zsh-keyring.asc to zsh.org/pub?
>
> That makes sense to me. I only didn't put it there because it wasn't there
> before (and again creating-a-release isn't quite explicit about it). I've
> added it now
Thanks. ENOTIME to update the creating-a-release.txt, sorry.
> On Sat 14 May 2022, at 16:50, Daniel Shahaf wrote:
> > For me, «wget --content-disposition
> > https://sourceforge.net/projects/zsh/files/zsh/5.9/zsh-5.9.tar.xz/download»
> > DTRTs with both wget 1.20.1-1.1 and wget 1.21.3-1+b1 on Debian (buster
> > and sid respectively).
>
> That one works as expected for me as well, but try with
> https://sourceforge.net/projects/zsh/files/zsh/5.9/zsh-5.9.tar.xz.asc/download
> instead. For that one, with wget 1.21.3 from Homebrew, i get:
>
> Saving to: ‘zsh-5.9.tar.xz.asc?viasf=1’
>
> Even though the headers contain:
>
> content-disposition: attachment; filename="zsh-5.9.tar.xz.asc"
>
I get "zsh-5.9.tar.xz.asc" with 1.20.1-1.1 (didn't test the other
version this time). I passed -S to wget and I see «Content-Disposition:
attachment; filename="zsh-5.9.tar.xz.asc"» in the second set of headers
and «Content-Type: application/octet-stream» without any
«Content-Disposition» in the third set of headers.
> On Sat 14 May 2022, at 16:50, Daniel Shahaf wrote:
> > I hope workers/43692 didn't break this…
>
> I checked the doc archive for 5.6.1, which was the last release before that
> change, and it looks like it contains basically the same files as it does
> now. And the man pages are still in the source archive as mentioned
Thanks, dana.
Daniel
next prev parent reply other threads:[~2022-05-14 23:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 20:59 dana
2022-05-14 21:50 ` Daniel Shahaf
2022-05-14 21:58 ` Daniel Shahaf
2022-05-14 22:27 ` dana
2022-05-14 23:26 ` Daniel Shahaf [this message]
2022-05-14 23:28 ` Daniel Shahaf
2022-05-14 23:50 ` dana
2022-05-15 10:36 ` Daniel Shahaf
2022-05-15 21:43 ` dana
2022-05-16 23:57 ` Phil Pennock
2022-05-21 1:31 ` Daniel Shahaf
2022-05-14 22:11 ` Axel Beckert
2022-05-14 22:31 ` dana
2022-05-15 4:33 ` Bart Schaefer
2022-05-15 6:00 ` dana
2022-05-14 23:21 ` Daniel Shahaf
2022-05-14 23:35 ` Axel Beckert
2022-05-14 23:49 ` Daniel Shahaf
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=20220514232605.GB13240@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=dana@dana.is \
--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).