Github messages for voidlinux
 help / color / mirror / Atom feed
From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libsixel: update to 1.10.2, switch upstream
Date: Mon, 27 Sep 2021 04:52:08 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33144@inbox.vuxu.org> (raw)

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

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

https://github.com/cinerea0/void-packages sixel
https://github.com/void-linux/void-packages/pull/33144

libsixel: update to 1.10.2, switch upstream
<!-- 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.)
- [ ] 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/33144.patch is attached

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

From 98686839374981b69209b6240bb2607a7fb68692 Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Sun, 26 Sep 2021 22:48:19 -0400
Subject: [PATCH] libsixel: update to 1.10.2, switch upstream

---
 common/shlibs             |  2 +-
 srcpkgs/libsixel/template | 14 +++++++-------
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/common/shlibs b/common/shlibs
index 2dbe14a7c6e6..5de62d0da829 100644
--- a/common/shlibs
+++ b/common/shlibs
@@ -3985,7 +3985,7 @@ libsmb-transport-samba4.so samba-libs-4.13.2_1
 libtdb-wrap-samba4.so samba-libs-4.13.3_1
 libutil-cmdline-samba4.so samba-libs-4.13.2_1
 libwinbind-client-samba4.so samba-libs-4.13.2_1
-libsixel.so.1 libsixel-1.8.6_1
+libsixel.so libsixel-1.10.2_1
 libpamtest.so.0 pam_wrapper-1.1.3_1
 libopenaptx.so.0 libopenaptx-0.2.0_1
 libsimavr.so.1 simavr-1.6_2
diff --git a/srcpkgs/libsixel/template b/srcpkgs/libsixel/template
index 8523f3b50ec0..5fb781e71bf6 100644
--- a/srcpkgs/libsixel/template
+++ b/srcpkgs/libsixel/template
@@ -1,15 +1,16 @@
 # Template file for 'libsixel'
 pkgname=libsixel
-version=1.8.6
+version=1.10.2
 revision=1
-build_style=gnu-configure
-makedepends="libpng-devel zlib-devel libjpeg-turbo-devel"
+build_style=meson
+hostmakedepends="pkg-config"
+makedepends="libjpeg-turbo-devel libpng-devel"
 short_desc="SIXEL encoder/decoder"
 maintainer="Andrew Benson <abenson+void@gmail.com>"
 license="MIT"
-homepage="https://github.com/saitoha/libsixel"
-distfiles="${homepage}/archive/v${version}.tar.gz"
-checksum=37611d60c7dbcee701346967336dbf135fdd5041024d5f650d52fae14c731ab9
+homepage="https://github.com/libsixel/libsixel"
+distfiles="https://github.com/libsixel/libsixel/archive/refs/tags/v${version}.tar.gz"
+checksum=a811b7f78c3b904661e02c753bcba064dbea3b6d46b4e0a61448f062327082f8
 
 libsixel-devel_package() {
 	short_desc+=" - development files"
@@ -18,7 +19,6 @@ libsixel-devel_package() {
 		vmove usr/bin/libsixel-config
 		vmove usr/include
 		vmove usr/lib/pkgconfig
-		vmove "usr/lib/*.a"
 		vmove "usr/lib/*.so"
 	}
 }

             reply	other threads:[~2021-09-27  2:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27  2:52 cinerea0 [this message]
2021-09-29 21:13 ` [WIP] " cinerea0
2021-09-29 22:18 ` dankamongmen
2021-09-30  0:49 ` cinerea0
2021-09-30  1:13 ` dankamongmen
2021-09-30  1:14 ` dankamongmen
2021-09-30  1:39 ` [PR PATCH] [Updated] " cinerea0
2021-09-30  3:27 ` [PR PATCH] [Updated] [WIP] libsixel: update to 1.10.3, " cinerea0
2021-09-30  3:32 ` cinerea0
2021-10-02 19:52 ` [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-33144@inbox.vuxu.org \
    --to=cinerea0@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).