Re: fail2ban missing as earmv6hf package

[Ramiro Aceves <ea1abz%gmail.com@localhost>]

I see in the bulk tracker that fail2ban indirectly failed because 2 failed python dependencies 

El 6 de junio de 2024 14:03:21 CEST, Ramiro Aceves <ea1abz%gmail.com@localhost> escribió:
>Hello Greg
>
>El jue, 6 jun 2024 a las 13:46, Greg Troxel (<gdt%lexort.com@localhost>) escribió:
>>
>> Ramiro Aceves <ea1abz%gmail.com@localhost> writes:
>>
>> > I just what to understand how  pkgsrc works.
>>
>> That's a really lengthy question :-)
>
>
>Thanks so much for answering.
>
>>
>> > I wanted to install fail2ban package in my RPiZeroW system but it
>> > seems not be be present as package:
>> >
>> > netbsd-raspaZeroW# pkgin se fail2ban
>> > No results found for fail2ban
>>
>> pkgsrc has control files per package and infrastructure files under mk/.
>> For lots of reasons, some things build on some platforms, and some
>> don't.
>>
>> > netbsd-raspaZeroW# cat /usr/pkg/etc/pkgin/repositories.conf
>> > https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/earmv6hf/10.0/All
>>
>> 10.0 is a symlink on the server.  At times people have been unwilling to
>> update the symlinks to point to newer builds.  You may wish to look at
>> the explicit 10.0_2024Q1 directories.
>
>Symbolic link now is pointing to 2024Q1 as I see under an ftp session
>on elinks. Indeed  2024Q1 is the version in which fail2ban disappears.
>
>If I download 2023Q4:
>
>netbsd-raspaZeroW$ wget
>https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/earmv6hf/10.0_2023Q4/All/pkg_summary.gz
>
>netbsd-raspaZeroW$ gunzip pkg_summary.gz
>
>netbsd-raspaZeroW$ cat pkg_summary |grep fail2ban
>PKGNAME=fail2ban-1.0.2nb2
>HOMEPAGE=http://www.fail2ban.org/
>PKGPATH=security/fail2ban
>FILE_NAME=fail2ban-1.0.2nb2.tgz
>DESCRIPTION=http://www.fail2ban.org/
>
>So I think fail2ban disappeard in 2024Q1.
>
>>
>> > I download manually pkg_summary.gz just to check:
>> >
>> > netbsd-raspaZeroW$ wget
>> > https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/earmv6hf/10.0/All/pkg_summary.gz
>> >
>> > netbsd-raspaZeroW$ gunzip pkg_summary.gz
>> >
>> > netbsd-raspaZeroW$ cat pkg_summary |grep fail2ban
>> > netbsd-raspaZeroW$
>> >
>> > There is no package on the summary.
>>
>> In general, any particualr package being missing from a binary package
>> set is not really that surprising.  earmv6 is becoming a bit crufty as
>> it is basically for the 1 and 0.  I suspect fairly few people, perhaps
>> 0, are spending time digging in.  But of course this is open source and
>> it's all available and anyone who wants to can.
>
>Oh, I know...
>>
>> > If I get the pkgsrc source tree:
>> >
>> > netbsd-raspaZeroW$ cat /usr/pkgsrc/CVS/Tag
>> > Tpkgsrc-2024Q1
>> >
>> > There is source for fail2ban
>>
>> sure.  that doesn't vanish if it fails to build, at least right away.
>>
>> > netbsd-raspaZeroW$ ls -lh /usr/pkgsrc/security/fail2ban/
>> > total 41K
>> > drwxr-xr-x   2 root  wheel  512B May 31 17:39 CVS
>> > -rw-r--r--   1 root  wheel  268B Feb  9  2015 DESCR
>> > -rw-r--r--   1 root  wheel  8.1K Nov 14  2023 Makefile
>> > -rw-r--r--   1 root  wheel   29K Jul  2  2023 PLIST
>> > -rw-r--r--   1 root  wheel  430B Jul  2  2023 distinfo
>> > drwxr-xr-x   3 root  wheel  512B May 31 15:54 files
>> > -rw-r--r--   1 root  wheel  269B Feb  9  2015 options.mk
>> > drwxr-xr-x   3 root  wheel  512B May 31 15:54 patches
>> > drwxr-xr-x  18 root  wheel  1.5K May 31 22:31 work
>> > netbsd-raspaZeroW$
>> >
>> > I compiled it and installed with no problems:
>> >
>> > netbsd-raspaZeroW$ pkgin list | grep ban
>> > fail2ban-1.0.2nb2    Scans log files and bans IP that makes too many
>> > password failures
>> >
>> > fail2ban works fine.
>>
>> That's a great success story.  I was getting ready to tell you to do that!
>>
>
>I was lucky.
>
>> > My question is. Why fail2ban is not ready as package? it is a matter
>> > of waiting for it to appear?
>>
>> You'd have to look at the bulk build logs.  I just looked on my saved
>> data from pkgsrc-bulk and I don't see it.  We are not really organized
>> about having them linked from the binary package sets.
>
>Thanks, I will look for the build logs.
>
>>
>> I'd say it is unlikely that it will appear, at this point.  But I don't
>> know.
>
>But if it builds on my system why did it disappear?
>
>Thankg Greg.
>Regards.
>
>>