From: ludo@gnu.org (Ludovic Courtès)
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: 30801-done@debbugs.gnu.org
Subject: bug#30801: Add opencv
Date: Thu, 10 May 2018 00:01:13 +0200 [thread overview]
Message-ID: <878t8sxzdi.fsf@gnu.org> (raw)
In-Reply-To: <20180507203547.3ae3cb35@alma-ubu> ("Björn Höfling"'s message of "Mon, 7 May 2018 20:35:47 +0200")
Hi Björn,
Björn Höfling <bjoern.hoefling@bjoernhoefling.de> skribis:
> Here is another update:
>
> * Kept it in one output.
> * No, there are no .a-files.
> * I tried to build the documentation, but somehow it did not work.
> Postponed for the next update.
> * Added more to the description.
> * The new ffmpeg 4.0 caused a core dump during test phase, so I set it
> explicitly to the old 3.4.
Awesome, thanks for looking into this.
> From 0e234430fec497d3c7702e288474e39d37cb8ae8 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Bj=C3=B6rn=20H=C3=B6fling?=
> <bjoern.hoefling@bjoernhoefling.de>
> Date: Fri, 16 Feb 2018 20:31:37 +0100
> Subject: [PATCH] gnu: Add opencv.
>
> * gnu/packages/image-processing.scm (opencv): New variable.
Applied!
‘guix lint’ reports this:
gnu/packages/image-processing.scm:201:2: opencv@3.4.1: probably vulnerable to CVE-2018-7712, CVE-2018-7713, CVE-2018-7714
Could you take a look? It could be that 3.4.2 is around the corner and
we’ll just update at that point; if not, we may have to apply upstream
patches for these issues.
Thank you!
Ludo’.
next prev parent reply other threads:[~2018-05-09 22:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 16:58 [bug#30801] [PATCH 0/1] Add opencv Björn Höfling
2018-03-13 17:07 ` [bug#30801] [PATCH 1/1] gnu: " Björn Höfling
2018-03-15 21:04 ` [bug#30801] [PATCH 0/1] " Ludovic Courtès
2018-03-31 22:26 ` Björn Höfling
2018-04-01 12:21 ` Ludovic Courtès
2018-05-07 18:35 ` [bug#30801] " Björn Höfling
2018-05-09 22:01 ` Ludovic Courtès [this message]
2018-05-11 9:51 ` Björn Höfling
2018-05-11 12:00 ` Ludovic Courtès
2018-05-12 23:42 ` Björn Höfling
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=878t8sxzdi.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30801-done@debbugs.gnu.org \
--cc=bjoern.hoefling@bjoernhoefling.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).