Github messages for voidlinux
 help / color / mirror / Atom feed
From: zdykstra <zdykstra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] zfsbootmenu: require ncurses for bin/tput
Date: Sun, 28 Feb 2021 01:04:41 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29108@inbox.vuxu.org> (raw)

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

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

https://github.com/zdykstra/void-packages master
https://github.com/void-linux/void-packages/pull/29108

zfsbootmenu: require ncurses for bin/tput
<!-- 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
-->


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

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

From 488f59f08bb8a1e46cbde7cc964ef351f2384cae Mon Sep 17 00:00:00 2001
From: Zach Dykstra <dykstra.zachary@gmail.com>
Date: Sat, 27 Feb 2021 18:03:41 -0600
Subject: [PATCH] zfsbootmenu: require ncurses for bin/tput

---
 srcpkgs/zfsbootmenu/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/zfsbootmenu/template b/srcpkgs/zfsbootmenu/template
index 4b36fd6865e..16e0d4f60b6 100644
--- a/srcpkgs/zfsbootmenu/template
+++ b/srcpkgs/zfsbootmenu/template
@@ -1,10 +1,10 @@
 # Template file for 'zfsbootmenu'
 pkgname=zfsbootmenu
 version=1.8.1
-revision=1
+revision=2
 build_style=gnu-makefile
 conf_files="/etc/zfsbootmenu/config.yaml"
-depends="dracut zfs kexec-tools bash pigz mbuffer
+depends="dracut zfs kexec-tools bash pigz mbuffer ncurses
  perl-Config-IniFiles perl-Sort-Versions perl-boolean perl-YAML-PP"
 short_desc="ZFS Boot Environment menu, implemented in Dracut"
 maintainer="Zach Dykstra <dykstra.zachary@gmail.com>"

             reply	other threads:[~2021-02-28  0:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-28  0:04 zdykstra [this message]
2021-02-28  0:06 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29108@inbox.vuxu.org \
    --to=zdykstra@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).