From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] package: add python-pam
Date: Fri, 5 Dec 2014 23:47:16 +0100 [thread overview]
Message-ID: <20141205234716.4295177e@free-electrons.com> (raw)
In-Reply-To: <1417623151-1895-1-git-send-email-peter@korsgaard.com>
Dear Peter Korsgaard,
On Wed, 3 Dec 2014 17:12:31 +0100, Peter Korsgaard wrote:
> Upstream is no longer available, so get the tarball + important patches from
> Fedora.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> v1 missed dealloc patch.
>
> package/Config.in | 1 +
> package/python-pam/0001-dealloc.patch | 25 ++++
> package/python-pam/0002-nofree.patch | 68 +++++++++++
> .../0003-memory-errors-CVE2012-1502.patch | 136 +++++++++++++++++++++
> package/python-pam/Config.in | 15 +++
> package/python-pam/python-pam.mk | 16 +++
> 6 files changed, 261 insertions(+)
> create mode 100644 package/python-pam/0001-dealloc.patch
> create mode 100644 package/python-pam/0002-nofree.patch
> create mode 100644 package/python-pam/0003-memory-errors-CVE2012-1502.patch
> create mode 100644 package/python-pam/Config.in
> create mode 100644 package/python-pam/python-pam.mk
It's a little bit annoying to package stuff for which there is no
upstream available anymore, but oh well.
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
(code reviewed, license checked, built and runtime tested on
ARM/uClibc)
Note however that the commit title for package additions should
normally be "<pkg>: new package", but it can be fixed while applying,
of course :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-05 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 16:12 [Buildroot] [PATCHv2] package: add python-pam Peter Korsgaard
2014-12-05 22:47 ` Thomas Petazzoni [this message]
2014-12-07 22:13 ` Thomas Petazzoni
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=20141205234716.4295177e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox