From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: exiv2: update to 0.28.1.
Date: Sat, 18 Nov 2023 22:41:28 +0100 [thread overview]
Message-ID: <20231118214128.Ml1Jq5n0zF1cUCdJi2KpuOfTeEpt8gcYz_4888mPo6E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46838@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]
There's a merged pull request on the void-packages repository
exiv2: update to 0.28.1.
https://github.com/void-linux/void-packages/pull/46838
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
TODO:
- [x] Fix `gwenview`'s failed checks (not really fixed but the exact same tests fail on master as well)
- [x] `test_exiv2` fails for `libextractor`
- [x] `kfilemetadata5` tests fail (same tests fail on master)
- [x] Fix `nufraw` cross-build
- [x] `digikam` fails to build
@Johnnynator ufraw has been [unmaintained since December 2016](https://sourceforge.net/p/ufraw/discussion/434060/thread/30b4249b/), and it doesn't build with this PR; here are the options:
- remove the package entirely
- replace it with the newer [nufraw](https://sourceforge.net/projects/nufraw/), which already has [an exiv 0.28.x patch floating around](https://aur.archlinux.org/cgit/aur.git/tree/exiv2-error.patch?h=nufraw)
- patch it to build with this PR
What do you think? (edit: `nufraw` now replaces `ufraw` in this PR)
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTItest_exiv2NG.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-11-18 21:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 0:10 [PR PATCH] exiv2: update to 0.28.0 mhmdanas
2023-10-23 0:20 ` [PR PATCH] [Updated] " mhmdanas
2023-11-01 17:23 ` mhmdanas
2023-11-01 17:26 ` mhmdanas
2023-11-01 18:11 ` mhmdanas
2023-11-02 19:42 ` biopsin
2023-11-03 20:00 ` [PR PATCH] [Updated] " mhmdanas
2023-11-03 20:18 ` mhmdanas
2023-11-04 21:57 ` [PR PATCH] [Updated] " mhmdanas
2023-11-06 20:17 ` mhmdanas
2023-11-06 20:18 ` mhmdanas
2023-11-06 20:19 ` mhmdanas
2023-11-06 20:20 ` mhmdanas
2023-11-12 13:04 ` biopsin
2023-11-12 15:01 ` mhmdanas
2023-11-12 22:54 ` [PR PATCH] [Updated] " mhmdanas
2023-11-12 22:55 ` exiv2: update to 0.28.1 mhmdanas
2023-11-13 0:00 ` [PR PATCH] [Updated] " mhmdanas
2023-11-15 17:40 ` mhmdanas
2023-11-15 17:57 ` mhmdanas
2023-11-16 15:12 ` [PR REVIEW] " sh1r4s3
2023-11-16 15:56 ` mhmdanas
2023-11-16 16:43 ` sh1r4s3
2023-11-16 21:50 ` [PR PATCH] [Updated] " mhmdanas
2023-11-16 21:51 ` [PR REVIEW] " mhmdanas
2023-11-18 15:57 ` [PR PATCH] [Updated] " mhmdanas
2023-11-18 21:41 ` classabbyamp [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=20231118214128.Ml1Jq5n0zF1cUCdJi2KpuOfTeEpt8gcYz_4888mPo6E@z \
--to=classabbyamp@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).