Re: [cgiwrap-users] Fwd: Question regarding cracklib2 mailing list and source repo

[Nathan N. <nn...@ne...>]

Try the dropbox url again... I've told it to replace the config.guess/sub with latest from git since they are reasonably 
accessible as individual files.

-- Nathan

On 12/05/2013 03:16 AM, snehal wrote:
> Hi Nathan,
>
> I tried to build the tar provided by you on ppc64le, however I see that config.guess file changes are missing for
> ppc64le in the tar provided by you.
> Config.guess file is available at
>
> http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD
>
> ----Or----
> I can send you patch for config.guess, let me know your preference.
>
> After adding config.guess patch for ppc64le support to the tar provided by you, I see all following files are generated.
>
> /*lib*# ls
> libcrack.a   libcrack.so    libcrack.so.2.9.0
> libcrack.la  libcrack.so.2  python2.7
>
> /*share*# ls
> cracklib  locale
>
> /*include*# ls
> crack.h  packer.h
>
> /*sbin*# ls
> cracklib-check   cracklib-packer    create-cracklib-dict
> cracklib-format  cracklib-unpacker
>
> It would be great if you incorporate config.guess changes and release tar...
>
> Awaiting your reply
>
> Thanks,
> Snehal
>
>
> On 12/03/2013 07:47 PM, Nathan Neulinger wrote:
>> This tarball was generated with a "current" Fedora 20 (not even released yet) host with libtool/autoconf/etc. pieces
>> as distributed on that platform.
>>
>> https://dl.dropboxusercontent.com/u/33773121/2013-12-03/cracklib-2.9.0.tar.gz
>>
>> Please see if it works for you. If that tarball DOES work for you, I'll be happy to do a new release with that build
>> environment.
>>
>> If it doesn't, I don't think I'm going to be integrating the changes you've requested as I'm not interested in making
>> the packaging of cracklib dependent on pieces that aren't present in current distributions or creating a tarball that
>> can't be reproduced without developers jumping through extra hoops.
>>
>> If you are packaging yourself, I would suggest just adding the 'regen with your preferred/updated libtool/etc' as part
>> of that packaging, but until those changes are included/accepted by mainstream linux distributions, they won't be
>> included here.
>>
>> -- Nathan
>>
>> On 12/03/2013 12:16 AM, snehal wrote:
>>> Hi Nathan,
>>>
>>> This is a gentle reminder to spin pkg with new config.guess and libtool.
>>>
>>> As per your suggestion, I did checkout SVN repo and did ./configure, make , make install
>>> which did work fine on ppc64le platform. You may see details in my previous mail.
>>>
>>> Awaiting new tar from you with ppc64le support
>>>
>>>
>>> Thanks in advance,
>>> Snehal
>>>
>>>
>>>
>>>
>>> On 11/18/2013 04:22 PM, snehal wrote:
>>>>
>>>> Hi Nathan,
>>>>
>>>> I did take SVN repo
>>>>    svn checkout svn://svn.code.sf.net/p/cracklib/code/trunk/cracklib
>>>>
>>>> Then did run autogen.sh , which generated new configuration file which supports ppc64le.
>>>> Did
>>>> ./configure
>>>> make
>>>> make install
>>>>
>>>> I see following output with new libtool version
>>>>
>>>> 1. Folders created
>>>> /svn_cracklib# ls
>>>> cracklib  cracklib.tar *include  lib  sbin  share*
>>>> 2. Binaries created
>>>> /**sbin**# ls
>>>> cracklib-check   cracklib-packer    create-cracklib-dict
>>>> cracklib-format  cracklib-unpacker
>>>> 3. /**share**# ls
>>>> cracklib  locale
>>>> 4. /**lib**# ls
>>>> libcrack.a  libcrack.la  libcrack.so  libcrack.so.2 libcrack.so.2.9.0
>>>> 5. /**include**# ls
>>>> crack.h  packer.h
>>>>
>>>> Let me know if this is what you would see
>>>> If yes, then you may spin the pkg again with new libtool and release tar for us.
>>>>
>>>>
>>>> Snehal
>>>>
>>>>
>>>>
>>>>
>>>> On 11/14/2013 08:09 PM, Nathan Neulinger wrote:
>>>>> Since you have the upstream tools (libtool / autoconf) installed with the updated components, have you tried just
>>>>> running autogen.sh in an svn checkout of cracklib and see if it all works?
>>>>>
>>>>>     svn checkout svn://svn.code.sf.net/p/cracklib/code/trunk/cracklib
>>>>>
>>>>> Problem is - I don't actually copy in those files manually - I just use the generated ones from autoconf/autoheader
>>>>> installed on my devel box.
>>>>>
>>>>> I'll try to find some time to install latest autoconf/libtool on my box (currently fc17 so a bit downlevel) and see
>>>>> if I can generate a tarball that will work for you, but would be good for you to run a test from svn first just to be
>>>>> certain it will solve the problem for you.
>>>>>
>>>>> -- Nathan
>>>>>
>>>>> On 11/14/2013 06:39 AM, snehal wrote:
>>>>>> Hi Nathan,
>>>>>>
>>>>>>   Alpha release of libtool is available at following location
>>>>>> ftp://alpha.gnu.org/gnu/libtool/libtool-2.4.2.418.tar.gz (1.6MB)
>>>>>> ftp://alpha.gnu.org/gnu/libtool/libtool-2.4.2.418.tar.xz (920KB)
>>>>>>
>>>>>> It would be great if you can install this new libtool which supports ppc64le,
>>>>>> and spin the pkg and let us know the new tar availability. We can test it on ppc64le architecture for you.
>>>>>>
>>>>>> Currently I used http://sourceforge.net/projects/cracklib/files/latest/download/cracklib-2.9.0.tar.gz
>>>>>> Which does not have ppc64le support.
>>>>>>
>>>>>> Also,
>>>>>> Latest config.guess and config.sub w/ ppc64le fix is available @
>>>>>>
>>>>>> http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD and
>>>>>> http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD respectively.
>>>>>>
>>>>>> Thanks in advance,
>>>>>> Snehal
>>>>>>
>>>>>>
>>>>>> On 10/23/2013 06:11 PM, Nathan Neulinger wrote:
>>>>>>> I'm the current maintainer for cracklib, however if you have patches to libtool.m4/config.guess - those need to go
>>>>>>> upstream to the maintainers of those packages - they are not part of cracklib package. If you're talking about
>>>>>>> changes
>>>>>>> to configure.ac, those would go to this package.
>>>>>>>
>>>>>>> cracklib repo is still svn based on sourceforge project page.
>>>>>>>
>>>>>>> -- Nathan
>>>>>>>
>>>>>>> On 10/23/2013 01:51 AM, snehal wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> I found your name in AUTHORS file of cracklib2 tarball. I tried search upstream source mailing list for this pkg,
>>>>>>>> however I could not find one for upstream source.
>>>>>>>>
>>>>>>>> We are in the process of adding support for new arch (ppc64le) and as part of that wanted to send patches for
>>>>>>>> libtool.m4/config.guess or configure as appropriate. In that context, I wanted to confirm the below
>>>>>>>> 1) Should we send patches to you or there is some other mailing list?
>>>>>>>> 2) I could not find git repo. Only debian git repo found
>>>>>>>> http:///git/.debian.org/?p=pkg-cracklib/pkg-cracklib./git
>>>>>>>> /Could you please point me to upstream git repo ?/
>>>>>>>> / 3) Who is the maintainer for this pkg ?
>>>>>>>>
>>>>>>>> Appreciate your response
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Snehal
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

-- 
------------------------------------------------------------
Nathan Neulinger                       nn...@ne...
Neulinger Consulting                   (573) 612-1412