Bug#683792: unblock: libseccomp/1.0.0-1

To: Kees Cook <kees@debian.org>
Cc: 683792@bugs.debian.org
Subject: Bug#683792: unblock: libseccomp/1.0.0-1
From: intrigeri <intrigeri@debian.org>
Date: Sun, 25 Nov 2012 09:41:32 +0100
Message-id: <[🔎] 85fw3yyszn.fsf@boum.org>
Reply-to: intrigeri <intrigeri@debian.org>, 683792@bugs.debian.org
In-reply-to: <[🔎] 85bof5zbfy.fsf@boum.org> (intrigeri@debian.org's message of "Sat, 10 Nov 2012 17:09:53 +0100")
References: <20120804003531.24817.68767.reportbug@localhost6.localdomain6> <1344074186.21252.2.camel@jacala.jungle.funky-badger.org> <[🔎] 85bof5zbfy.fsf@boum.org>

Hi Kees,

intrigeri wrote (10 Nov 2012 16:09:53 GMT) :
> I am not sure I exactly get the usecase for this unblock request.

> Is it developers who will need the -dev package to compile their new
> software with seccomp features in? (Those probably can easily install
> 1.0.0-1 from the backports, if it does not make it into Wheezy.)

> Is it users who would want to install third-party software that was
> compiled against the libseccomp 1.0 ABI?

> Anything else?

Ping?

Cheers,
--
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc

Reply to:

References:
- Bug#683792: unblock: libseccomp/1.0.0-1
  - From: intrigeri <intrigeri@debian.org>

Prev by Date: Bug#694297: unblock: tex-common/3.14
Next by Date: Bug#689706: unblock: gpa/0.9.3-1
Previous by thread: Bug#683792: unblock: libseccomp/1.0.0-1
Next by thread: Bug#690464:
Index(es):
- Date
- Thread