From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: kdesu security update needed
Date: Mon, 3 Oct 2016 17:47:25 -0400 [thread overview]
Message-ID: <20161003214725.GA28207@jasmine> (raw)
In-Reply-To: <87eg3xnmhb.fsf@gnu.org>
On Mon, Oct 03, 2016 at 11:36:48PM +0200, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
>
> > On Sat, Oct 01, 2016 at 02:19:05PM +0200, Ludovic Courtès wrote:
> >> Leo Famulari <leo@famulari.name> skribis:
> >> > An aside, the CVE linter gives false positives for grafted packages. For
> >> > example, try `guix lint -c cve openssl@1.0`.
> >>
> >> That’s been annoying me for some time so I’d like to see if we can
> >> improve grafting in a way that would allow us to use a different version
> >> number in the package replacement, which in turn would allow ‘guix lint’
> >> to see the right version number of the replacement.
> >
> > That would be nice. The current situation (with misleading package
> > versions) is a huge improvement over what we had before, but I think
> > that users should not need to understand the implementation details of
> > grafting to determine the version of packages.
> >
> > I always figured this quirky limitation was a side-effect of rushing to
> > implement recursive grafting before OpenSSL 1.0.2g was released.
>
> Done in commit 57bdd79e485801ccf405ca7389bd099809fe5d67! And with
> 9bee2bd1b02c7ef91cc7232e8647bd07525d3382, ‘guix lint -c cve openssl@1.0’
> reports the right thing (zero known CVEs).
Awesome :)
next prev parent reply other threads:[~2016-10-03 21:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 15:23 kdesu security update needed Leo Famulari
2016-09-29 18:35 ` David Craven
2016-09-29 18:52 ` David Craven
2016-09-29 20:49 ` Leo Famulari
2016-10-01 12:19 ` Ludovic Courtès
2016-10-01 12:59 ` David Craven
2016-10-02 13:34 ` Ludovic Courtès
2016-10-01 16:37 ` Leo Famulari
2016-10-03 21:36 ` Ludovic Courtès
2016-10-03 21:47 ` Leo Famulari [this message]
2016-09-29 21:34 ` Leo Famulari
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=20161003214725.GA28207@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.