Github messages for voidlinux
 help / color / mirror / Atom feed
From: tsndqst <tsndqst@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] containerd: update to 1.4.3.
Date: Sat, 13 Feb 2021 16:25:25 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28734@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1885 bytes --]

There is a new pull request by tsndqst against master on the void-packages repository

https://github.com/tsndqst/void-packages containerd-1.4
https://github.com/void-linux/void-packages/pull/28734

containerd: update to 1.4.3.
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->

There was a previous [pull request](https://github.com/void-linux/void-packages/pull/27116) to update to 1.4.3  but the EOL date was not clear for 1.3.  https://github.com/containerd/containerd/blob/master/RELEASES.md#support-horizon indicates the EOL date for 1.3 is in a couple weeks.

A patch file from https://github.com/void-linux/void-packages/pull/28734.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-containerd-1.4-28734.patch --]
[-- Type: text/x-diff, Size: 1148 bytes --]

From 42eaf7df572537a68d5fa6b00c650118e4fce0fd Mon Sep 17 00:00:00 2001
From: Tim Sandquist <tim.sandquist@gmail.com>
Date: Sat, 13 Feb 2021 09:13:36 -0600
Subject: [PATCH] containerd: update to 1.4.3.

---
 srcpkgs/containerd/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/containerd/template b/srcpkgs/containerd/template
index fd8d1b10195..33f3d27a061 100644
--- a/srcpkgs/containerd/template
+++ b/srcpkgs/containerd/template
@@ -1,7 +1,7 @@
 # Template file for 'containerd'
 pkgname=containerd
-version=1.3.9
-revision=2
+version=1.4.3
+revision=1
 build_style=go
 go_import_path=github.com/containerd/containerd
 go_package="${go_import_path}/cmd/containerd
@@ -20,7 +20,7 @@ maintainer="Paul Knopf <pauldotknopf@gmail.com>"
 license="Apache-2.0"
 homepage="https://github.com/containerd/containerd"
 distfiles="https://github.com/containerd/containerd/archive/v${version}.tar.gz"
-checksum=9244212589c84b12262769dca6fb985c0c680cb5259c8904b29c511d81fd62d0
+checksum=@6069273fb93a162a2a11e29ef3b631c92ed1b4942be461f781a2aabbaed97701
 make_dirs="/var/lib/containerd 0755 root root"
 
 post_build() {

             reply	other threads:[~2021-02-13 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-13 15:25 tsndqst [this message]
2021-02-14 19:09 ` Gottox
2021-02-14 19:35 ` ericonr
2021-02-15 14:34 ` [PR PATCH] [Updated] " tsndqst
2021-02-15 17:17 ` [PR PATCH] [Merged]: " ericonr
  -- strict thread matches above, loose matches on Subject: below --
2020-12-13  1:15 [PR PATCH] " ndowens

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28734@inbox.vuxu.org \
    --to=tsndqst@users.noreply.github.com \
    --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).