From: ap4y <ap4y@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] WIP packer: update to 1.6.3
Date: Mon, 28 Sep 2020 09:18:50 +0200 [thread overview]
Message-ID: <20200928071850.1ZmInFLDb1yQWDLVgDsfavFkh3f2kKM2bhYuoiGJR-A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25142@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
There is an updated pull request by ap4y against master on the void-packages repository
https://github.com/ap4y/void-packages packer-1.6.3
https://github.com/void-linux/void-packages/pull/25142
WIP packer: update to 1.6.3
Overflow issue on 32-bit platforms was fixed upstream:
- https://github.com/Azure/azure-sdk-for-go/issues/1993
- https://github.com/hashicorp/packer/pull/6479
A patch file from https://github.com/void-linux/void-packages/pull/25142.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-packer-1.6.3-25142.patch --]
[-- Type: text/x-diff, Size: 1306 bytes --]
From 10b7742595f99462c560a73566ab730d8095c04f Mon Sep 17 00:00:00 2001
From: ap4y <mail@ap4y.me>
Date: Mon, 28 Sep 2020 18:44:29 +1300
Subject: [PATCH] packer: update to 1.6.3
Overflow issue on 32-bit platforms was fixed upstream:
- https://github.com/Azure/azure-sdk-for-go/issues/1993
- https://github.com/hashicorp/packer/pull/6479
---
srcpkgs/packer/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/packer/template b/srcpkgs/packer/template
index 246fa292daf..bfb82b8c3c9 100644
--- a/srcpkgs/packer/template
+++ b/srcpkgs/packer/template
@@ -1,6 +1,6 @@
# Template file for 'packer'
pkgname=packer
-version=1.6.0
+version=1.6.3
revision=1
build_style=go
go_import_path="github.com/hashicorp/packer"
@@ -9,9 +9,9 @@ maintainer="Andrea Brancaleoni <abc@pompel.me>"
license="MPL-2.0"
homepage="http://www.packer.io"
distfiles="https://${go_import_path}/archive/v${version}.tar.gz"
-checksum=2a135643a837ad58df16e4acc3ac01ad32b61643722a6a027929bbd6baba9435
+checksum=6e92920cef2a30b231cb08cffc5410ff1b7e0921da0c6dea70cdb10684ed73ae
replaces="packer-bin>=0"
case "$XBPS_TARGET_MACHINE" in
- i686*|arm*) broken="https://build.voidlinux.org/builders/i686_builder/builds/9375/steps/shell_3/logs/stdio";;
+ arm*) go_ldflags="-linkmode=external";;
esac
next prev parent reply other threads:[~2020-09-28 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 5:47 [PR PATCH] " ap4y
2020-09-28 6:39 ` [PR PATCH] [Updated] " ap4y
2020-09-28 7:00 ` ap4y
2020-09-28 7:18 ` ap4y [this message]
2020-09-29 13:50 ` [PR PATCH] [Merged]: " ahesford
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=20200928071850.1ZmInFLDb1yQWDLVgDsfavFkh3f2kKM2bhYuoiGJR-A@z \
--to=ap4y@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).