Github messages for voidlinux
 help / color / mirror / Atom feed
From: Bnyro <Bnyro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] jpegoptim: update to 1.5.4.
Date: Tue, 11 Jul 2023 09:11:14 +0200	[thread overview]
Message-ID: <20230711071114.50IkjEZt5_F7JwMcSUlqaviEjV-Hjw9d0QSAZfJTTQs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44964@inbox.vuxu.org>

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

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

https://github.com/Bnyro/void-packages jpegoptim
https://github.com/void-linux/void-packages/pull/44964

jpegoptim: update to 1.5.4.
<!-- 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, x86_64-glibc



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

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

From aeb3fa3a0ad3470f37bc8e495fadc80f7e581511 Mon Sep 17 00:00:00 2001
From: Bnyro <bnyro@tutanota.com>
Date: Tue, 11 Jul 2023 09:11:09 +0200
Subject: [PATCH] jpegoptim: update to 1.5.4, orphan

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

diff --git a/srcpkgs/jpegoptim/template b/srcpkgs/jpegoptim/template
index 94aa3dc031f1..cedffea7c213 100644
--- a/srcpkgs/jpegoptim/template
+++ b/srcpkgs/jpegoptim/template
@@ -1,13 +1,13 @@
 # Template file for 'jpegoptim'
 pkgname=jpegoptim
-version=1.5.2
+version=1.5.4
 revision=1
 build_style=gnu-configure
 makedepends="libjpeg-turbo-devel"
 short_desc="Utility to optimize/compress JPEG files"
-maintainer="archaeme <normandy@firemail.cc>"
+maintainer="Orphaned <orphan@voidlinux.org>"
 license="GPL-3.0-or-later"
 homepage="https://github.com/tjko/jpegoptim"
 changelog="https://raw.githubusercontent.com/tjko/jpegoptim/master/README"
 distfiles="https://github.com/tjko/jpegoptim/archive/refs/tags/v${version}.tar.gz"
-checksum=e8701cc85c065e05747a15da72ebb403056ebecaa98e2806cf69cdd443397910
+checksum=8fc7537f722d533ea8b45966ab80c83e3342d088d5a690fdadfb05b7c9cba47f

  parent reply	other threads:[~2023-07-11  7:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 14:54 [PR PATCH] " Bnyro
2023-07-10 20:57 ` classabbyamp
2023-07-11  7:10 ` [PR PATCH] [Updated] " Bnyro
2023-07-11  7:11 ` Bnyro [this message]
2023-07-12  1:29 ` [PR PATCH] [Merged]: jpegoptim: update to 1.5.4, orphan classabbyamp

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=20230711071114.50IkjEZt5_F7JwMcSUlqaviEjV-Hjw9d0QSAZfJTTQs@z \
    --to=bnyro@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).