From: RunningDroid <RunningDroid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] weechat: point changelog at the new file
Date: Tue, 04 Jun 2024 01:37:03 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50672@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
There is a new pull request by RunningDroid against master on the void-packages repository
https://github.com/RunningDroid/void-packages weechat_changelog
https://github.com/void-linux/void-packages/pull/50672
weechat: point changelog at the new file
Upstream converted their changelog from AsciiDoc to MarkDown: weechat/weechat@826042176796b6322d2bd8264239adc9a774788f
<!-- Uncomment relevant sections and delete options which are not applicable -->
<!--
#### 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/50672.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-weechat_changelog-50672.patch --]
[-- Type: text/x-diff, Size: 1041 bytes --]
From 5031f5f621bbd092fe38cbf60575ab0efe03f049 Mon Sep 17 00:00:00 2001
From: RunningDroid <runningdroid@zoho.com>
Date: Mon, 3 Jun 2024 19:19:57 -0400
Subject: [PATCH] weechat: point changelog at the new file
Upstream converted their changelog from AsciiDoc to MarkDown
---
srcpkgs/weechat/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/weechat/template b/srcpkgs/weechat/template
index e4b496cf035ecb..3a81fea73476ac 100644
--- a/srcpkgs/weechat/template
+++ b/srcpkgs/weechat/template
@@ -16,7 +16,7 @@ short_desc="Fast, light and extensible IRC client"
maintainer="Leah Neukirchen <leah@vuxu.org>"
license="GPL-3.0-or-later"
homepage="https://www.weechat.org"
-changelog="https://raw.githubusercontent.com/weechat/weechat/master/ChangeLog.adoc"
+changelog="https://raw.githubusercontent.com/weechat/weechat/master/CHANGELOG.md"
distfiles="https://www.weechat.org/files/src/weechat-${version}.tar.xz"
checksum=157e22a17dcc303c665739631a04470d786474e805febed2ed2d5b6250d18653
lib32disabled=yes
next reply other threads:[~2024-06-03 23:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 23:37 RunningDroid [this message]
2024-06-04 0:12 ` [PR PATCH] [Merged]: " 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50672@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).