From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: gnome-software: update to 43.3.
Date: Wed, 11 Jan 2023 23:53:07 +0100 [thread overview]
Message-ID: <20230111225307.Wvtz8W0UdbXWEcmx6-4I_5aWWdGepSLKNk0C49dIcM0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41588@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
There's a merged pull request on the void-packages repository
gnome-software: update to 43.3.
https://github.com/void-linux/void-packages/pull/41588
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
Also fixes a gnome-software crash related to libsoup2
(note: libostree still depends on libsoup2 even with `--with-curl`, but that should be fine https://github.com/ostreedev/ostree/blob/1fb9404612f3d98d329f0129ecbc6c8225823679/configure.ac#L137)
<!--
#### 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
-->
prev parent reply other threads:[~2023-01-11 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 11:36 [PR PATCH] Fix gsoftware oreo639
2023-01-11 22:37 ` [PR PATCH] [Updated] gnome-software: update to 43.3 oreo639
2023-01-11 22:53 ` paper42 [this message]
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=20230111225307.Wvtz8W0UdbXWEcmx6-4I_5aWWdGepSLKNk0C49dIcM0@z \
--to=paper42@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).