From: RunningDroid <RunningDroid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] optipng: add changelog
Date: Wed, 29 May 2024 05:00:29 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50579@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]
There is a new pull request by RunningDroid against master on the void-packages repository
https://github.com/RunningDroid/void-packages optipng_changelog
https://github.com/void-linux/void-packages/pull/50579
optipng: add changelog
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
`xchangelog` handles it fine, the file itself starts with non-printing characters* for some reason though:
![2024-05-28T22:53:50,555115731-04:00](https://github.com/void-linux/void-packages/assets/486393/19e58d7f-6976-4f15-b908-40f2bb494467)
*: byte sequence is `EF BB BF`
<!--
#### 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/50579.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-optipng_changelog-50579.patch --]
[-- Type: text/x-diff, Size: 793 bytes --]
From 435f0c264d03b9bff97ccbf7412a0b4b2cf3a394 Mon Sep 17 00:00:00 2001
From: RunningDroid <runningdroid@zoho.com>
Date: Tue, 28 May 2024 22:41:37 -0400
Subject: [PATCH] optipng: add changelog
---
srcpkgs/optipng/template | 1 +
1 file changed, 1 insertion(+)
diff --git a/srcpkgs/optipng/template b/srcpkgs/optipng/template
index e82b59cc0de4fb..0c6966e1be898a 100644
--- a/srcpkgs/optipng/template
+++ b/srcpkgs/optipng/template
@@ -8,6 +8,7 @@ short_desc="Advanced PNG Optimizer"
maintainer="Orphaned <orphan@voidlinux.org>"
license="Zlib"
homepage="https://optipng.sourceforge.net/"
+changelog="https://optipng.sourceforge.net/history.txt"
distfiles="${SOURCEFORGE_SITE}/optipng/optipng-${version}.tar.gz"
checksum=25a3bd68481f21502ccaa0f4c13f84dcf6b20338e4c4e8c51f2cefbd8513398c
next reply other threads:[~2024-05-29 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 3:00 RunningDroid [this message]
2024-05-29 10:28 ` classabbyamp
2024-05-29 10:29 ` [PR PATCH] [Merged]: " classabbyamp
2024-05-29 10:30 ` classabbyamp
2024-05-29 10:30 ` classabbyamp
2024-05-29 22:34 ` RunningDroid
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-50579@inbox.vuxu.org \
--to=runningdroid@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).