Github messages for voidlinux
 help / color / mirror / Atom feed
From: skmpz <skmpz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] snappy: update to 1.1.10.
Date: Thu, 20 Apr 2023 15:15:45 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43541@inbox.vuxu.org> (raw)

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

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

https://github.com/skmpz/void-packages snappy-1.1.10
https://github.com/void-linux/void-packages/pull/43541

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

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### 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/43541.patch is attached

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

From 842e6846372645268b93c2f58035d4d788c1404e Mon Sep 17 00:00:00 2001
From: skmpz <dem.procopiou@gmail.com>
Date: Thu, 20 Apr 2023 17:15:09 +0400
Subject: [PATCH] snappy: update to 1.1.10.

---
 srcpkgs/snappy/patches/inline.patch | 11 -----------
 srcpkgs/snappy/template             |  4 ++--
 2 files changed, 2 insertions(+), 13 deletions(-)
 delete mode 100644 srcpkgs/snappy/patches/inline.patch

diff --git a/srcpkgs/snappy/patches/inline.patch b/srcpkgs/snappy/patches/inline.patch
deleted file mode 100644
index a69dfecaf48f..000000000000
--- a/srcpkgs/snappy/patches/inline.patch
+++ /dev/null
@@ -1,11 +0,0 @@
-Add inline with SNAPPY_ATTRIBUTE_ALWAYS_INLINE on AdvanceToNextTag to fix:
-1097 |         size_t tag_type = AdvanceToNextTag(&ip, &tag);
-     |                           ~~~~~~~~~~~~~~~~^~~~~~~~~~~
-../snappy.cc:1017:8: error: inlining failed in call to 'always_inline'
-'size_t snappy::AdvanceToNextTag(const uint8_t**, size_t*)': function body can be overwritten at link time
-
---- a/snappy.cc	2021-05-05 02:53:34.000000000 +0400
-+++ b/snappy.cc	2021-05-24 01:24:59.124654893 +0400
-@@ -1017 +1017 @@ SNAPPY_ATTRIBUTE_ALWAYS_INLINE
--size_t AdvanceToNextTag(const uint8_t** ip_p, size_t* tag) {
-+inline size_t AdvanceToNextTag(const uint8_t** ip_p, size_t* tag) {
diff --git a/srcpkgs/snappy/template b/srcpkgs/snappy/template
index 7e9e5214fb7d..f85fcac828c6 100644
--- a/srcpkgs/snappy/template
+++ b/srcpkgs/snappy/template
@@ -1,6 +1,6 @@
 # Template file for 'snappy'
 pkgname=snappy
-version=1.1.9
+version=1.1.10
 revision=1
 build_style=cmake
 configure_args="-DBUILD_SHARED_LIBS=1"
@@ -10,7 +10,7 @@ maintainer="skmpz <dem.procopiou@gmail.com>"
 license="BSD-3-Clause"
 homepage="https://google.github.io/snappy"
 distfiles="https://github.com/google/snappy/archive/${version}.tar.gz"
-checksum=75c1fbb3d618dd3a0483bff0e26d0a92b495bbe5059c8b4f1c962b478b6e06e7
+checksum=49d831bffcc5f3d01482340fe5af59852ca2fe76c3e05df0e67203ebbe0f1d90
 
 post_install() {
 	vlicense COPYING

             reply	other threads:[~2023-04-20 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20 13:15 skmpz [this message]
2023-04-30  2:25 ` [PR PATCH] [Merged]: " abenson

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