Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated]  editline: update to 1.17.0
Date: Mon, 06 Jan 2020 17:16:54 +0100	[thread overview]
Message-ID: <20200106161654.X58erR2jGcXrQfj-o6VG5eUHv6nWSyYFYF5lyCA6wos@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18072@inbox.vuxu.org>

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

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

https://github.com/ndowens/void-packages editline
https://github.com/void-linux/void-packages/pull/18072

 editline: update to 1.17.0 
Bumped nix as there was a SONAME change, even though xbps didn't detect it. Upstream stated 1.0.1 -> 1.0.2. Verified by building old and new and there was a difference.

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

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

From 6144dce42e8854ed477259335d6e4e861c8faa2f Mon Sep 17 00:00:00 2001
From: Nathan Owens <ndowens04@gmail.com>
Date: Mon, 6 Jan 2020 08:18:53 -0600
Subject: [PATCH] editline: update to 1.17.0

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

diff --git a/srcpkgs/editline/template b/srcpkgs/editline/template
index 50f10aab097..e010c39a329 100644
--- a/srcpkgs/editline/template
+++ b/srcpkgs/editline/template
@@ -1,6 +1,6 @@
 # Template file for 'editline'
 pkgname=editline
-version=1.16.1
+version=1.17.0
 revision=1
 build_style=gnu-configure
 short_desc="Minimal readline() replacement"
@@ -8,7 +8,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="Spencer-94"
 homepage="http://troglobit.com/projects/editline/"
 distfiles="https://github.com/troglobit/editline/releases/download/${version}/editline-${version}.tar.xz"
-checksum=6518cc0d8241bcebc860432d1babc662a9ce0f5d6035649effe38b5bc9463f8c
+checksum=257fbf1f92eeb401d448f5a7f5e108416afd0f5979c5cbab2ea3010e0152ee93
 
 post_install() {
 	rm -rf ${DESTDIR}/usr/share/doc

  parent reply	other threads:[~2020-01-06 16:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06 14:54 [PR PATCH] " voidlinux-github
2020-01-06 16:12 ` voidlinux-github
2020-01-06 16:12 ` voidlinux-github
2020-01-06 16:14 ` voidlinux-github
2020-01-06 16:14 ` voidlinux-github
2020-01-06 16:14 ` voidlinux-github
2020-01-06 16:14 ` voidlinux-github
2020-01-06 16:15 ` voidlinux-github
2020-01-06 16:15 ` voidlinux-github
2020-01-06 16:16 ` voidlinux-github
2020-01-06 16:16 ` voidlinux-github
2020-01-06 16:16 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-06 16:16 ` voidlinux-github [this message]
2020-01-06 16:17 ` voidlinux-github
2020-01-06 16:17 ` voidlinux-github
2020-01-06 16:18 ` voidlinux-github
2020-01-06 16:18 ` voidlinux-github
2020-01-06 16:20 ` voidlinux-github
2020-01-06 16:20 ` voidlinux-github
2020-01-10 18:09 ` [PR PATCH] [Merged]: " voidlinux-github
2020-01-10 18:09 ` voidlinux-github

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=20200106161654.X58erR2jGcXrQfj-o6VG5eUHv6nWSyYFYF5lyCA6wos@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).