From: "Ludovic Courtès" <ludo@gnu.org>
To: Michael Rohleder <mike@rohleder.de>
Cc: 42542@debbugs.gnu.org
Subject: [bug#42542] [PATCH] gnu: libextractor: Update to 1.10.
Date: Sun, 26 Jul 2020 18:05:22 +0200 [thread overview]
Message-ID: <87pn8i2rel.fsf@gnu.org> (raw)
In-Reply-To: <87h7tv5dhi.fsf@rohleder.de> (Michael Rohleder's message of "Sun, 26 Jul 2020 02:25:29 +0200")
Hello!
Michael Rohleder <mike@rohleder.de> skribis:
> After reading about the exciting dkgpg pkg, I wanted to try gnunet the
> other day and noticed that libextractor doesnt build, because of some
> test failures in exiv2 tests:
>
> ...
> =================================================
> libextractor 1.9: src/plugins/test-suite.log
> ==================================================
>
> # TOTAL: 29
> # PASS: 28
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> FAIL: test_exiv2
> ================
>
> Warning: Directory Pentax, entry 0x0004: Data area exceeds data buffer, ignoring it.
> Got additional meta data of type 38 and format 1 with value `28deg 8' 18"' from plugin `exiv2'
> Got additional meta data of type 40 and format 1 with value `14deg 14' 22"' from plugin `exiv2'
> Did not get expected meta data of type 38 and format 1 with value `28deg 8' 17.585" ' from plugin `exiv2'
> Did not get expected meta data of type 40 and format 1 with value `14deg 14' 21.713" ' from plugin `exiv2'
> FAIL test_exiv2 (exit status: 1)
Does upstream libextractor have a fix for that? It would seem that the
new exiv2 rounds that geolocation meta data.
I’m not comfortable using an older exiv2 version, because this is code
that’s potentially given untrusted input, so it would be nicer if we
could fix this test!
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-07-26 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 0:25 [bug#42542] [PATCH] gnu: libextractor: Update to 1.10 Michael Rohleder
2020-07-26 16:05 ` Ludovic Courtès [this message]
2020-07-27 2:07 ` Michael Rohleder
2020-07-28 1:16 ` Michael Rohleder
2020-07-28 21:54 ` bug#42542: " Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pn8i2rel.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=42542@debbugs.gnu.org \
--cc=mike@rohleder.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).