From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] cracklib: New package
Date: Wed, 5 Apr 2017 16:29:53 +0200 [thread overview]
Message-ID: <20170405162953.3619c506@free-electrons.com> (raw)
In-Reply-To: <1491396001.3239.1.camel@spectralink.com>
Hello,
On Wed, 5 Apr 2017 12:40:02 +0000, S?rensen, Stefan wrote:
> > Could you have a look into this, and submit an updated version that
> > fixes this issue?
>
> I am not able to reproduce this, though I just notices that it uses the
> cracklib tools from the PATH, not the ones built in host-cracklib, so
> maybe that is what is causing the issue.
I'm not sure it's the problem, because I'm pretty sure I ran the
command manually by explicitly calling the tools built in
output/host/usr/bin.
But anyway, I'll test your next iteration, and see if I can still
reproduce the issue.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-05 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 13:45 [Buildroot] [PATCH 1/4] libscrypt: New package Stefan Sørensen
2017-02-09 13:45 ` [Buildroot] [PATCH 2/4] cracklib: " Stefan Sørensen
2017-04-01 21:15 ` Thomas Petazzoni
2017-04-05 12:40 ` Sørensen, Stefan
2017-04-05 14:29 ` Thomas Petazzoni [this message]
2017-02-09 13:45 ` [Buildroot] [PATCH 3/4] libpwquality: " Stefan Sørensen
2017-04-01 21:21 ` Thomas Petazzoni
2017-02-09 13:45 ` [Buildroot] [PATCH 4/4] DEVELOPERS: Add Stefan Sørensen for cracklib, libpwquality and libscrypt Stefan Sørensen
2017-03-12 22:57 ` [Buildroot] [PATCH 1/4] libscrypt: New package 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=20170405162953.3619c506@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