Github messages for voidlinux
 help / color / mirror / Atom feed
From: ashpooljh <ashpooljh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] xen-hypervisor: fix install into /boot/boot
Date: Sat, 08 Aug 2020 18:28:09 +0200	[thread overview]
Message-ID: <20200808162809.HCz52gji8b0qKdIOH735gCRdkauJ9U_dBrjHPVC5G8Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24139@inbox.vuxu.org>

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

There is an updated pull request by ashpooljh against master on the void-packages repository

https://github.com/ashpooljh/void-packages xen-hypervisor-fix-install
https://github.com/void-linux/void-packages/pull/24139

xen-hypervisor: fix install into /boot/boot
fix #17612
`[ci skip]` due to [exceeding](https://travis-ci.org/github/ashpooljh/void-packages/jobs/716090891#L29182) the maximum log length allowed by Travis.

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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-xen-hypervisor-fix-install-24139.patch --]
[-- Type: text/x-diff, Size: 888 bytes --]

From 84ef40a401938f7f9dfb04d40fda70878e74d3ef Mon Sep 17 00:00:00 2001
From: Artem Zhurikhin <ashpool@xecut.net>
Date: Sat, 8 Aug 2020 13:53:52 +0300
Subject: [PATCH] xen-hypervisor: fix install into /boot/boot

fix #17612
[ci skip]
---
 srcpkgs/xen/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/xen/template b/srcpkgs/xen/template
index ae8f5e246fc..9ba85981992 100644
--- a/srcpkgs/xen/template
+++ b/srcpkgs/xen/template
@@ -1,7 +1,7 @@
 # Template file for 'xen'
 pkgname=xen
 version=4.10.4
-revision=3
+revision=4
 # grep -R IPXE_GIT_TAG src/xen-*/tools/firmware/etherboot
 _git_tag_ipxe=356f6c1b64d7a97746d1816cef8ca22bdd8d0b5d
 archs="x86_64*"
@@ -201,7 +201,7 @@ xen-hypervisor_package() {
 	short_desc="Xen Hypervisor"
 	nostrip_files="xen-syms-${version}"
 	pkg_install() {
-		vmove boot
+		vmove "boot/*"
 		vmove usr/lib/efi
 	}
 }

  parent reply	other threads:[~2020-08-08 16:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-08 11:43 [PR PATCH] " ashpooljh
2020-08-08 11:54 ` [PR PATCH] [Updated] " ashpooljh
2020-08-08 14:33 ` ericonr
2020-08-08 14:33 ` ericonr
2020-08-08 16:27 ` [PR PATCH] [Updated] " ashpooljh
2020-08-08 16:28 ` ashpooljh [this message]
2020-08-08 21:11 ` jnbr
2020-08-08 21:11 ` [PR PATCH] [Merged]: " jnbr

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=20200808162809.HCz52gji8b0qKdIOH735gCRdkauJ9U_dBrjHPVC5G8Y@z \
    --to=ashpooljh@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).