From: BlueChrystal <BlueChrystal@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] vagrant: update to 2.2.16.
Date: Mon, 24 May 2021 00:12:22 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31081@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1663 bytes --]
There is a new pull request by BlueChrystal against master on the void-packages repository
https://github.com/BlueChrystal/void-packages vagrant-2.2.16_1
https://github.com/void-linux/void-packages/pull/31081
vagrant: update to 2.2.16.
<!-- 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?
- [ ] 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
Sorry, I have no idea how I'm supposed to test this.
<!--
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
-->
A patch file from https://github.com/void-linux/void-packages/pull/31081.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-vagrant-2.2.16_1-31081.patch --]
[-- Type: text/x-diff, Size: 1015 bytes --]
From 06c6a03e412fd049e71c849c7e1f4596c5be7890 Mon Sep 17 00:00:00 2001
From: BlueChrystal <84290062+BlueChrystal@users.noreply.github.com>
Date: Mon, 24 May 2021 01:11:25 +0300
Subject: [PATCH] vagrant: update to 2.2.16.
---
srcpkgs/vagrant/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/vagrant/template b/srcpkgs/vagrant/template
index c7f3cdcd2de9..647d0abc0060 100644
--- a/srcpkgs/vagrant/template
+++ b/srcpkgs/vagrant/template
@@ -1,6 +1,6 @@
# Template file for 'vagrant'
pkgname=vagrant
-version=2.2.15
+version=2.2.16
revision=1
archs="i686 x86_64*"
hostmakedepends="ruby"
@@ -11,7 +11,7 @@ maintainer="Andrea Brancaleoni <abc@pompel.me>"
license="MIT"
homepage="https://www.vagrantup.com/"
distfiles="https://github.com/mitchellh/${pkgname}/archive/v${version}.tar.gz"
-checksum=98c9c726d5cb7e46793b4505f3d907b2a0673e0f6e43997c218a0be5330cc83f
+checksum=ab3c60bb12b2da916fd073192849f2b5d3f224f95febf3538212247c4cde28d6
nocross=yes
post_extract() {
next reply other threads:[~2021-05-23 22:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 22:12 BlueChrystal [this message]
2021-05-24 22:07 ` ericonr
2021-05-24 23:15 ` BlueChrystal
2021-05-26 10:22 ` [PR PATCH] [Merged]: " thypon
2021-05-25 0:15 [PR PATCH] " jonagoldman
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-31081@inbox.vuxu.org \
--to=bluechrystal@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).