all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: 31487@debbugs.gnu.org
Subject: [bug#31487] [PATCH] gnu: Add upx.
Date: Mon, 28 May 2018 09:55:01 +0200	[thread overview]
Message-ID: <878t8443l6.fsf@gnu.org> (raw)
In-Reply-To: <87muwli52v.fsf@gmail.com> (Pierre Neidhardt's message of "Sun, 27 May 2018 15:46:48 +0200")

Hi Pierre,

Pierre Neidhardt <ambrevar@gmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> There’s one issue left though:
>>
>>   $ ./pre-inst-env guix lint upx
>>   gnu/packages/compression.scm:2179:2: upx@3.94: probably vulnerable to CVE-2017-15056, CVE-2017-16869
>>
>> Could you check whether patches are available for these?  Better be safe
>> than sorry!
>
> Indeed they are.
> They are not on the master branch though, only devel I think.
> So what's the protocol here?  Shall we cherry-pick the fixing commits or
> get latest devel?

Yes.  You can add them as individual patches (see commit
aa8ac0294421d465f60e18c8271f971ec8407a95 for an example); as usual, make
sure each patch starts with a few lines explaining what the patch does
and where it comes from (you can take the commit log for that plus a
repo URL, for instance.)

Then you can check that ‘guix lint upx’ is happy.

TIA!

Ludo’.

  reply	other threads:[~2018-05-28  7:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 22:51 [bug#31487] [PATCH] gnu: Add upx Pierre Neidhardt
2018-05-18  6:46 ` Pierre Neidhardt
2018-05-26 20:14 ` Ludovic Courtès
2018-05-27 13:46   ` Pierre Neidhardt
2018-05-28  7:55     ` Ludovic Courtès [this message]
2018-05-29  6:42       ` Pierre Neidhardt
2018-05-29 13:27         ` Ludovic Courtès
2018-06-15  7:12           ` Ludovic Courtès
2018-06-16 14:58             ` Pierre Neidhardt
2018-06-16 19:15               ` Pierre Neidhardt
2018-06-16 14:54 ` [bug#31487] [PATCH] gnu: upx: Fix CVE-2017-15056 Pierre Neidhardt
2018-06-16 21:57   ` bug#31487: " 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878t8443l6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=31487@debbugs.gnu.org \
    --cc=ambrevar@gmail.com \
    /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.