From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libsoup: update to 2.47.3.
Date: Sat, 24 Feb 2024 02:44:30 +0100 [thread overview]
Message-ID: <20240224014430.AB27D250ED@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48891@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
There is an updated pull request by oreo639 against master on the void-packages repository
https://github.com/oreo639/void-packages libsoup2
https://github.com/void-linux/void-packages/pull/48891
libsoup: update to 2.47.3.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
Note: Updating to this version adds checks such that applications mixing libsoup3 and libsoup2 will abort with an error message.
<!--
#### 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/48891.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libsoup2-48891.patch --]
[-- Type: text/x-diff, Size: 1069 bytes --]
From 4c6bc86a4fbc678db8b8c0221494e93ecce7af8f Mon Sep 17 00:00:00 2001
From: oreo639 <oreo6391@gmail.com>
Date: Fri, 23 Feb 2024 02:07:22 -0800
Subject: [PATCH] libsoup: update to 2.74.3.
---
srcpkgs/libsoup/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/libsoup/template b/srcpkgs/libsoup/template
index 71bf1b2f7632f1..395d5e1aa971c6 100644
--- a/srcpkgs/libsoup/template
+++ b/srcpkgs/libsoup/template
@@ -1,6 +1,6 @@
# Template file for 'libsoup'
pkgname=libsoup
-version=2.74.0
+version=2.74.3
revision=1
build_style=meson
build_helper="gir"
@@ -17,7 +17,7 @@ license="LGPL-2.1-or-later"
homepage="https://wiki.gnome.org/Projects/libsoup"
changelog="https://gitlab.gnome.org/GNOME/libsoup/-/raw/libsoup-2-74/NEWS"
distfiles="${GNOME_SITE}/libsoup/${version%.*}/libsoup-${version}.tar.xz"
-checksum=33b1d4e0d639456c675c227877e94a8078d731233e2d57689c11abcef7d3c48e
+checksum=e4b77c41cfc4c8c5a035fcdc320c7bc6cfb75ef7c5a034153df1413fa1d92f13
make_check=no # gio tests can't run in chroot
# Package build options
next prev parent reply other threads:[~2024-02-24 1:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 10:09 [PR PATCH] " oreo639
2024-02-24 1:40 ` sgn
2024-02-24 1:44 ` oreo639 [this message]
2024-02-24 1:44 ` libsoup: update to 2.74.3 oreo639
2024-03-04 13:23 ` [PR PATCH] [Updated] " oreo639
2024-04-09 11:59 ` sgn
2024-04-09 19:22 ` oreo639
2024-04-09 23:22 ` [PR PATCH] [Merged]: " sgn
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=20240224014430.AB27D250ED@inbox.vuxu.org \
--to=oreo639@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).