Github messages for voidlinux
 help / color / mirror / Atom feed
From: glaulher <glaulher@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] smenu: update to 0.9.18.
Date: Sun, 06 Jun 2021 18:44:20 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31326@inbox.vuxu.org> (raw)

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

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

https://github.com/glaulher/void-packages smenu
https://github.com/void-linux/void-packages/pull/31326

smenu: update to 0.9.18.
<!-- 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
- [x] 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.)
- [x] I built this PR locally for my native architecture, (ARCH-LIBC)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [x] aarch64-musl
  - [x] armv7l
  - [ ] armv6l-musl
-->


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

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

From 3068ada2cc173ed5f8ab732e5e953dad590dad61 Mon Sep 17 00:00:00 2001
From: glaulher <glaulher.developer@gmail.com>
Date: Sun, 6 Jun 2021 13:42:20 -0300
Subject: [PATCH] smenu: update to 0.9.18.

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

diff --git a/srcpkgs/smenu/template b/srcpkgs/smenu/template
index fed55aeabbee..90b17761704b 100644
--- a/srcpkgs/smenu/template
+++ b/srcpkgs/smenu/template
@@ -1,6 +1,6 @@
 # Template file for 'smenu'
 pkgname=smenu
-version=0.9.17
+version=0.9.18
 revision=1
 build_style=gnu-configure
 makedepends="ncurses-devel"
@@ -9,6 +9,6 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="GPL-2.0-only"
 homepage="https://github.com/p-gen/smenu"
 distfiles="https://github.com/p-gen/smenu/archive/v${version}.tar.gz"
-checksum=f9d174af52d92725710dbcfe3905d511901f810849d81d3f6fc6c51c30bebc7f
+checksum=08d4f58edb432522da61f94372a78c812a1fee324a31a60f432283715fa56d37
 
 LDFLAGS="-lncurses"

             reply	other threads:[~2021-06-06 16:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-06 16:44 glaulher [this message]
2021-06-07 14:07 ` [PR PATCH] [Merged]: " ericonr

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-31326@inbox.vuxu.org \
    --to=glaulher@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).