From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: containerd: update to 1.3.2
Date: Thu, 26 Dec 2019 09:29:19 +0100 [thread overview]
Message-ID: <20191226082919.-uTQUKcHhCirs4lTYKxXIGsvG3EErW7OwpNBS_bXs8s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17555@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
There's a merged pull request on the void-packages repository
containerd: update to 1.3.2
https://github.com/void-linux/void-packages/pull/17555
Description:
Is there a reason that this package is so far behind (+1000 commits since the last version), when Docker and runc are up-to-date?
I also don't know how to resolve this go build error:
```sh
#package github.com/containerd/containerd/cmd/containerd-release:
#/builddir/containerd-1.3.2/_build-containerd-xbps/src/github.com/containerd/containerd
#exists but
#/builddir/containerd-1.3.2/_build-containerd-xbps/src/github.com/containerd/containerd/.git
#does not - stale checkout?
```
parent reply other threads:[~2019-12-26 8:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17555@inbox.vuxu.org>]
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=20191226082919.-uTQUKcHhCirs4lTYKxXIGsvG3EErW7OwpNBS_bXs8s@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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).