From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: libopenraw: split the pixbuf loader into subpackage
Date: Sat, 02 Jul 2022 08:05:20 +0200 [thread overview]
Message-ID: <20220702060520.ZjZC9jmiIAF_BDZFOsn63zHZg95OEu9jSt1NmG8NIKA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37749@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]
There's a merged pull request on the void-packages repository
libopenraw: split the pixbuf loader into subpackage
https://github.com/void-linux/void-packages/pull/37749
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
Someone had this issue on the GNOME matrix, libopenraw-pixbuf-loader wasn't loading their CR2 file correctly and I can reproduce it.
Without the libopenraw pixbufloader, eog was able to load the CR2 file correctly. The pixbuf loader is currently apart of the libopenraw package which is a dependency of xfce thumbler.
Seeing as the pixbuf loader part isn't needed by xfce or eog and the pixbuf loader is considered deprecated upstream, probably best to split it into its own subpackage so people can install it if they really need it.
https://gitlab.freedesktop.org/libopenraw/libopenraw/-/issues/10
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-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:[~2022-07-02 6:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 23:05 [PR PATCH] " oreo639
2022-06-29 23:07 ` [PR PATCH] [Updated] " oreo639
2022-06-30 10:09 ` [PR REVIEW] " Duncaen
2022-06-30 17:26 ` oreo639
2022-06-30 17:34 ` [PR PATCH] [Updated] " oreo639
2022-07-01 14:23 ` [PR REVIEW] " sgn
2022-07-01 18:36 ` [PR PATCH] [Updated] " oreo639
2022-07-01 18:37 ` [PR REVIEW] " oreo639
2022-07-02 6:05 ` sgn [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=20220702060520.ZjZC9jmiIAF_BDZFOsn63zHZg95OEu9jSt1NmG8NIKA@z \
--to=sgn@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).