Github messages for voidlinux
 help / color / mirror / Atom feed
From: xeroxslayer <xeroxslayer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libsoup3: update to 3.6.0
Date: Wed, 25 Sep 2024 12:40:20 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52346@inbox.vuxu.org> (raw)

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

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

https://github.com/xeroxslayer/void-packages libsoup3
https://github.com/void-linux/void-packages/pull/52346

libsoup3: update to 3.6.0
#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture: **x86_64-musl**
- I built this PR locally for these architectures:
  - x86_64
  - aarch64-musl
  - aarch64
  - i686
  - i686-musl
  - armv7l
  - armv7l-musl
  - armv6l
  - armv6l-musl

The builds are built the preferred way, i.e. match arch word size and libc in the build environments (for example, aarch64-musl in x86_64-musl, armv6l in i386, etc.).

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

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

From 22dc82eba76d4bf49ad61df2911c948b20019ac2 Mon Sep 17 00:00:00 2001
From: xeroxslayer <xeroxslayer@proton.me>
Date: Wed, 25 Sep 2024 12:22:45 +0200
Subject: [PATCH] libsoup3: update to 3.6.0

---
 srcpkgs/libsoup3/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/libsoup3/template b/srcpkgs/libsoup3/template
index a95256e13d2bdd..aecff9263be5bd 100644
--- a/srcpkgs/libsoup3/template
+++ b/srcpkgs/libsoup3/template
@@ -1,6 +1,6 @@
 # Template file for 'libsoup3'
 pkgname=libsoup3
-version=3.4.2
+version=3.6.0
 revision=1
 build_style=meson
 build_helper="gir"
@@ -18,7 +18,7 @@ license="LGPL-2.1-or-later"
 homepage="https://wiki.gnome.org/Projects/libsoup"
 changelog="https://gitlab.gnome.org/GNOME/libsoup/-/raw/master/NEWS"
 distfiles="${GNOME_SITE}/libsoup/${version%.*}/libsoup-${version}.tar.xz"
-checksum=78c8fa37cb152d40ec8c4a148d6155e2f6947f3f1602a7cda3a31ad40f5ee2f3
+checksum=62959f791e8e8442f8c13cedac8c4919d78f9120d5bb5301be67a5e53318b4a3
 make_check=ci-skip # can not bind ports in CI
 
 # Package build options

             reply	other threads:[~2024-09-25 10:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25 10:40 xeroxslayer [this message]
2024-12-25  1:58 ` github-actions
2025-01-08  1:59 ` [PR PATCH] [Closed]: " github-actions

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