Github messages for voidlinux
 help / color / mirror / Atom feed
From: klardotsh <klardotsh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] elinks: update to 0.17.0.
Date: Wed, 03 Jan 2024 08:19:03 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48041@inbox.vuxu.org> (raw)

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

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

https://github.com/klardotsh/void-packages klardotsh/update-elinks
https://github.com/void-linux/void-packages/pull/48041

elinks: update to 0.17.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly** (loaded my own https-based site with it to test a thing, it worked. haven't extensively tested anything else really)

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- 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/48041.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-klardotsh/update-elinks-48041.patch --]
[-- Type: text/x-diff, Size: 1147 bytes --]

From 72f24a16d5e596956865f9b7a0824de52ee2907d Mon Sep 17 00:00:00 2001
From: Josh Klar <josh@klar.sh>
Date: Tue, 2 Jan 2024 23:17:26 -0800
Subject: [PATCH] elinks: update to 0.17.0.

---
 srcpkgs/elinks/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/elinks/template b/srcpkgs/elinks/template
index 8193bacf83cad..55c62244f2d65 100644
--- a/srcpkgs/elinks/template
+++ b/srcpkgs/elinks/template
@@ -1,7 +1,7 @@
 # Template file for 'elinks'
 pkgname=elinks
-version=0.16.0
-revision=2
+version=0.17.0
+revision=1
 build_style=gnu-configure
 configure_args="--enable-true-color --enable-fastmem --without-spidermonkey"
 hostmakedepends="automake libtool pkg-config gettext"
@@ -13,7 +13,7 @@ license="GPL-2.0-only"
 homepage="https://github.com/rkd77/elinks"
 changelog="https://raw.githubusercontent.com/rkd77/elinks/master/NEWS"
 distfiles="https://github.com/rkd77/elinks/archive/v${version}.tar.gz"
-checksum=5494a73737eeb182fe2333b74e9b6192170f583c7722a0650dcd14ef088b9dfb
+checksum=250a55198bb3e16a49a52fde85ffc54f1e654b7615369467725a3d74bc469f22
 # ld: no input files
 disable_parallel_build=yes
 

             reply	other threads:[~2024-01-03  7:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03  7:19 klardotsh [this message]
2024-01-03 12:27 ` [PR PATCH] [Merged]: " sgn

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