supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Alexis <flexibeast@gmail.com>
To: alice <alice@ayaya.dev>
Cc: "skaware@list.skarnet.org" <skaware@list.skarnet.org>,
	supervision@list.skarnet.org
Subject: Re: [announce] skarnet.org February 2023 release
Date: Sun, 19 Feb 2023 18:48:18 +1100	[thread overview]
Message-ID: <87k00e5byx.fsf@ada> (raw)
In-Reply-To: <CQMCEMY6UFB6.QZ6RS1A6FS9C@sumire>


*sigh* Sorry everyone. The execline-man-pages release _also_ 
 failed to include a Makefile update (to include execline.1, the 
 man page for the new multicall binary). So there's a new release 
 tag:

* 
  https://github.com/flexibeast/execline-man-pages/releases/tag/v2.9.2.0.2

Hopefully everything is now in order!


"alice" <alice@ayaya.dev> writes:

> On Sun Feb 19, 2023 at 7:39 AM CET, Alexis wrote:
>>
>> "alice" <alice@ayaya.dev> writes:
>>
>> > On Sun Feb 19, 2023 at 6:39 AM CET, Alexis wrote:
>>
>> >>   https://github.com/flexibeast/s6-portable-utils-man-pages/releases/tag/v2.3.0.0.1
>> >
>> > these (s6-portable-utils-man-pages) fail to make install, 
>> > because
>> > s6-test.1 was removed.
>>
>> Gah, sorry about that! This should now be fixed.
>
> thanks! works now.
>
> don't mean to backseat the release process too much, but you 
> should
> generally
> not retag a new commit (breaks history of the tag for whoever 
> already
> had it,
> cached tarballs (me, funnily), ..), rather just release .2 .

      parent reply	other threads:[~2023-02-19  7:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 15:33 Laurent Bercot
2023-02-19  5:39 ` Alexis
2023-02-19  6:17   ` alice
2023-02-19  6:39     ` Alexis
2023-02-19  6:58       ` alice
2023-02-19  7:38         ` Alexis
2023-02-19  8:12           ` alice
2023-02-19  7:48         ` Alexis [this message]

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=87k00e5byx.fsf@ada \
    --to=flexibeast@gmail.com \
    --cc=alice@ayaya.dev \
    --cc=skaware@list.skarnet.org \
    --cc=supervision@list.skarnet.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.
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).