Re: What is oficial list of ARCHS for NOT_FOR_ARCHS / ONLY_FOR_ARCHS?
Lev Serebryakovwrites: > Hello Freebsd-ports, > > I'm confused, should I use "arm64" or "aarch64" and how to spell > mips(el?)(64?32?) properly. ${ARCH} ~ ${MACHINE_ARCH} (uname -p). As the ports framework doesn't expose ${MACHINE} (uname -m) you're stuck listing every supported arm/mips flavor unless you override e.g., ONLY_FOR_ARCHS= aarch64 amd64 arm armeb armv6 armv6hf i386 \ mips mips64 mips64el mipsel mipsn32 powerpc \ powerpc64 sparc64 vs. ARCH= ${MACHINE} ONLY_FOR_ARCHS= amd64 arm arm64 i386 mips pc98 powerpc sparc64 # Translates to MACHINE/MACHINE_ARCH during runtime $ make targets -C /usr/src Supported TARGET/TARGET_ARCH pairs for world and kernel targets amd64/amd64 arm/arm arm/armeb arm/armv6 arm/armv6hf arm64/aarch64 i386/i386 mips/mipsel mips/mips mips/mips64el mips/mips64 mips/mipsn32 pc98/i386 powerpc/powerpc powerpc/powerpc64 sparc64/sparc64 -- MACHINE and MACHINE_ARCH are defined by make(1) itself but not documented in the man page. signature.asc Description: PGP signature
Re: make index failing on databases/tarantool
On 3 November 2015 at 18:24, Kurt Jaegerwrote: > Hi! > >> --- describe.databases --- >> make[5]: "/usr/ports/databases/tarantool/Makefile" line 56: Malformed >> conditional (defined(USE_GCC) && ${USE_GCC} == yes && ${GCC_DEFAULT} >> == 4.8) >> make[5]: Fatal errors encountered -- cannot continue===> >> databases/tarantool failed >> *** [describe.databases] Error code 1 >> >> make[2]: stopped in /usr/ports >> >> There's nothing special in /etc/make.conf. > > I have a different line 56 for that file, so what ports tree version > do you have ? Looks like commit 400686 has fixed the problem. Thanks! -- Jonathan Chen ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: fail2ban fails to build (fwd)
On Tue, 3 Nov 2015, Kubilay Kocak wrote: > Have you tried deleting pkg, making sure you're grabbing the latest > packages, and reinstalling pkg? > > a) pkg should not be segfaulting > b) if you're not on the latest pkg version, the bug could have already > been fixed OK, I did a bit more digging, and found that during one of my more desperate i.e. less lucid moments I had renamed /var/db/pkg to .../pkg.old in an attempt to load all of ports again, which I now remember was failing because of a FreeBSD version mismatch[*]. Looks like pkg got upset and crashed... Anyway, here's what you wanted (after I renamed it back): pkg-1.5.3 > succeeds port (port has 1.2.7) So yeah, I'm outta date, so I have some work to do... [*] Because this is a binary-only system (as supplied to me), the script to bump the patch level is not present, but it gets incremented on a kernel update, thus we have: aneurin# uname -r 9.3-RELEASE-p21 but I know it's at p29 because I faithfully track all updates. No matter what mirror or technique (FTP/HTTP) was used to load "ports" I get something like "not found on this server" or something, so I gave up; it was looking for -p21 but only say -p25 was available. Does that make sense? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: fail2ban fails to build (fwd)
On 3/11/2015 3:53 PM, Dave Horsfall wrote: > On Tue, 3 Nov 2015, Kubilay Kocak wrote: > >> Have you tried deleting pkg, making sure you're grabbing the latest >> packages, and reinstalling pkg? >> >> a) pkg should not be segfaulting >> b) if you're not on the latest pkg version, the bug could have already >> been fixed > > OK, I did a bit more digging, and found that during one of my more > desperate i.e. less lucid moments I had renamed /var/db/pkg to .../pkg.old > in an attempt to load all of ports again, which I now remember was failing > because of a FreeBSD version mismatch[*]. Looks like pkg got upset and > crashed... > > Anyway, here's what you wanted (after I renamed it back): > > pkg-1.5.3 > succeeds port (port has 1.2.7) > > So yeah, I'm outta date, so I have some work to do... Definitely. What's not better is what you have installed is later than what pkg thinks there is (db mismatch or out of sync) > [*] > Because this is a binary-only system (as supplied to me), the script to > bump the patch level is not present, but it gets incremented on a kernel > update, thus we have: > > aneurin# uname -r > 9.3-RELEASE-p21 What script, freebsd-update? > but I know it's at p29 because I faithfully track all updates. How are you tracking them? > No matter what mirror or technique (FTP/HTTP) was used to load "ports" I > get something like "not found on this server" or something, so I gave up; > it was looking for -p21 but only say -p25 was available. > > Does that make sense? Kinda/Mostly :) When you say "load ports", what do you mean and what method exactly are you using to do it? You said earlier you're using binary packages only, but here you say ports. Are we using these terms interchangeably here? If so, cool, if not, confusing :) I'm not sure whether or to what extent your potential system (mis?)configuration is contributing to these "not found on this server" errors. What exactly is showing you this error? ./koobs ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg : option to exclude some files from checksum ?
On Mon, Nov 02, 2015 at 12:35:10AM +0100, Xavier wrote: > Hi folks, > > I noticed that some ports are complaining in daily check that a checksum > has changed. > > Example : f-prot which checksums virus definitions, which obviously changes. > > Is there some macro/option in Makefile to not checksum this file ? > > I hope my point is clear enough... > > TIA, > > Xav make -DNO_CHECKSUM should work pgpjnxgal6Wn1.pgp Description: PGP signature
Re: pkg : option to exclude some files from checksum ?
On Mon, Nov 02, 2015 at 12:35:10AM +0100, Xavier wrote: > Hi folks, > > I noticed that some ports are complaining in daily check that a checksum > has changed. > > Example : f-prot which checksums virus definitions, which obviously changes. > > Is there some macro/option in Makefile to not checksum this file ? > > I hope my point is clear enough... > > TIA, > > Xav It is a bug in the f-prot package/ports, no ports should checksum volatile information/db. Bapt signature.asc Description: PGP signature
Re: What is oficial list of ARCHS for NOT_FOR_ARCHS / ONLY_FOR_ARCHS?
Hello Lev, I'm confused, should I use "arm64" or "aarch64" and how to spell mips(el?)(64?32?) properly. That is a good question. I scanned through /usr/ports/Mk/bsd.ports.mk. ARCH is documented as: "The architecture of the target machine, such as would be returned by "uname -p"." I tried to find the related source-code, but stopped - currently i'm to short on time. But i hope this gives you a good pointer. Greetings, Torsten ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg : option to exclude some files from checksum ?
On Mon, Nov 02, 2015 at 03:19:15PM -0800, Don Lewis wrote: > On 2 Nov, Lars Engels wrote: > > On Mon, Nov 02, 2015 at 12:35:10AM +0100, Xavier wrote: > >> Hi folks, > >> > >> I noticed that some ports are complaining in daily check that a checksum > >> has changed. > >> > >> Example : f-prot which checksums virus definitions, which obviously > >> changes. > >> > >> Is there some macro/option in Makefile to not checksum this file ? > >> > >> I hope my point is clear enough... > >> > >> TIA, > >> > >> Xav > > > > make -DNO_CHECKSUM should work > > Does it make sense to include stale virus definitions in the package? > Why not just download the up to date definitions at runtime? > I agree that is what the port should do Bapt signature.asc Description: PGP signature
Re: pkg : option to exclude some files from checksum ?
On 2 Nov, Lars Engels wrote: > On Mon, Nov 02, 2015 at 12:35:10AM +0100, Xavier wrote: >> Hi folks, >> >> I noticed that some ports are complaining in daily check that a checksum >> has changed. >> >> Example : f-prot which checksums virus definitions, which obviously changes. >> >> Is there some macro/option in Makefile to not checksum this file ? >> >> I hope my point is clear enough... >> >> TIA, >> >> Xav > > make -DNO_CHECKSUM should work Does it make sense to include stale virus definitions in the package? Why not just download the up to date definitions at runtime? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
fail2ban fails to build (fwd)
Anyone like to comment? I don't know Python, nor am I familiar with the more subtle aspects of the ports area. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." -- Forwarded message -- Date: Fri, 16 Oct 2015 05:02:20 +1100 (EST) From: Dave HorsfallTo: FreeBSD Ports Subject: fail2ban fails to build 9.3-RELEASE-p21 ===> Registering installation for py27-setuptools27-2.0.1 as automatic pkg-static: Error parsing manifest: error while parsing /usr/ports/devel/py-setuptools27/work/.metadir/+MANIFEST: line: 9, column: 25 - 'invalid character in a key', character: ',' *** [fake-pkg] Error code 74 Seems to be related to the trailing ',' here: categories: [devel,python,] Simply removing the comma made no difference, so I assume the file got regenerated from somewhere. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
make index failing on databases/tarantool
Hi, I've just updated to revision 400683 on a 10.2-STABLE/amd64 host , and a "make index" is currently failing with: --- describe.databases --- make[5]: "/usr/ports/databases/tarantool/Makefile" line 56: Malformed conditional (defined(USE_GCC) && ${USE_GCC} == yes && ${GCC_DEFAULT} == 4.8) make[5]: Fatal errors encountered -- cannot continue===> databases/tarantool failed *** [describe.databases] Error code 1 make[2]: stopped in /usr/ports There's nothing special in /etc/make.conf. Cheers -- Jonathan Chen___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
texinfo.tex file size mismatch
Hi, I was trying to install seafile from ports on FreeBSD 10.2-RELEASE machine, but I'm stuck at texinfo installation. Is there any way around to get it installed? Thanks :/usr/ports/www/seahub # make install ===> Staging for seahub-4.0.5_1 ===> seahub-4.0.5_1 depends on file: /usr/local/www/haiwen/seafile-server/seafile/bin/seaf-server - not found ===> seafile-4.0.6_3 depends on executable: valac - not found ===> vala-0.28.1 depends on executable: bison - not found ===> bison-2.7.1,1 depends on package: m4>=1.4.16,1 - not found ===> m4-1.4.17_1,1 depends on executable: makeinfo - not found ===> Found saved configuration for texinfo-6.0.20151013 ===> texinfo-6.0.20151013 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by texinfo-6.0.20151013 for building ===> Extracting for texinfo-6.0.20151013 => SHA256 Checksum OK for texinfo/6.0.20151013/texinfo-6.0.tar.xz. => SHA256 Checksum OK for texinfo/6.0.20151013/htmlxref.cnf. => SHA256 Checksum mismatch for texinfo/6.0.20151013/texinfo.tex. => SHA256 Checksum OK for texinfo/6.0.20151013/texi2dvi. ===> Refetch for 1 more times files: texinfo/6.0.20151013/texinfo.tex ===> Found saved configuration for texinfo-6.0.20151013 ===> texinfo-6.0.20151013 depends on file: /usr/local/sbin/pkg - found => texinfo.tex doesn't seem to exist in /usr/ports/distfiles/texinfo/6.0.20151013. => Attempting to fetch ftp://ftp.stack.nl/pub/users/johans/texinfo/20151013/texinfo.tex fetch: ftp://ftp.stack.nl/pub/users/johans/texinfo/20151013/texinfo.tex: Forbidden => Attempting to fetch http://ftpmirror.gnu.org/texinfo/texinfo.tex fetch: http://ftpmirror.gnu.org/texinfo/texinfo.tex: size mismatch: expected 349424, actual 353514 => Attempting to fetch http://ftp.gnu.org/gnu/texinfo/texinfo.tex fetch: http://ftp.gnu.org/gnu/texinfo/texinfo.tex: size mismatch: expected 349424, actual 353514 => Attempting to fetch ftp://ftp.gnu.org/gnu/texinfo/texinfo.tex fetch: ftp://ftp.gnu.org/gnu/texinfo/texinfo.tex: Forbidden => Attempting to fetch http://www.gtlib.gatech.edu/pub/gnu/gnu/texinfo/texinfo.tex fetch: http://www.gtlib.gatech.edu/pub/gnu/gnu/texinfo/texinfo.tex: Internal Server Error => Attempting to fetch http://mirrors.kernel.org/gnu/texinfo/texinfo.tex fetch: http://mirrors.kernel.org/gnu/texinfo/texinfo.tex: size mismatch: expected 349424, actual 353514 => Attempting to fetch ftp://ftp.kddlabs.co.jp/GNU/gnu/texinfo/texinfo.tex fetch: ftp://ftp.kddlabs.co.jp/GNU/gnu/texinfo/texinfo.tex: Forbidden => Attempting to fetch ftp://ftp.dti.ad.jp/pub/GNU/texinfo/texinfo.tex fetch: ftp://ftp.dti.ad.jp/pub/GNU/texinfo/texinfo.tex: Forbidden => Attempting to fetch ftp://ftp.mirrorservice.org/sites/ftp.gnu.org/gnu/texinfo/texinfo.tex fetch: ftp://ftp.mirrorservice.org/sites/ftp.gnu.org/gnu/texinfo/texinfo.tex: Forbidden => Attempting to fetch ftp://ftp.informatik.hu-berlin.de/pub/gnu/gnu/texinfo/texinfo.tex fetch: ftp://ftp.informatik.hu-berlin.de/pub/gnu/gnu/texinfo/texinfo.tex: Forbidden => Attempting to fetch ftp://ftp.informatik.rwth-aachen.de/pub/mirror/ftp.gnu.org/pub/gnu/texinfo/texinfo.tex fetch: ftp://ftp.informatik.rwth-aachen.de/pub/mirror/ftp.gnu.org/pub/gnu/texinfo/texinfo.tex: Forbidden => Attempting to fetch http://ftp.funet.fi/pub/gnu/prep/texinfo/texinfo.tex fetch: http://ftp.funet.fi/pub/gnu/prep/texinfo/texinfo.tex: size mismatch: expected 349424, actual 353514 => Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/texinfo/6.0.20151013/texinfo.tex fetch: http://distcache.FreeBSD.org/ports-distfiles/texinfo/6.0.20151013/texinfo.tex: Not Found => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles/texinfo/6.0.20151013 and try again. *** Error code 1 Stop. make[11]: stopped in /usr/ports/print/texinfo *** Error code 1 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: fail2ban fails to build (fwd)
On 3/11/2015 11:10 AM, Dave Horsfall wrote: > Anyone like to comment? I don't know Python, nor am I familiar with the > more subtle aspects of the ports area. > Hi Dave, I can't reproduce the issue building/testing security/py-fail2ban with poudriere. The error included in your original post though, appears to be related to the devel/py-setuptools27 port, not fail2ban itself. I can't reproduce the error testing that port either. The error you get "invalid character in a key" looks like a libucl error message, a format that pkg uses for the MANIFEST file. Can you attach `pkg version -v` output please. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: fail2ban fails to build (fwd)
On Tue, 3 Nov 2015, Kubilay Kocak wrote: Hi! > Can you attach `pkg version -v` output please. Child process pid=74392 terminated abnormally: Segmentation fault: 11 Hmmm... To be honest, I think my ports area is a little scrambled right now, due to some sort of a mistake when going to the new package system. GDB is not much use, because PKG has been stripped (this is a binary-only system). I guess it'll have to await my new server running FreeBSD 10 (I cannot upgrade this one, as it's my only production box, and the hardware's days are numbered). Thanks anyway. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: fail2ban fails to build (fwd)
On 3/11/2015 2:11 PM, Dave Horsfall wrote: > On Tue, 3 Nov 2015, Kubilay Kocak wrote: > > Hi! > >> Can you attach `pkg version -v` output please. > > Child process pid=74392 terminated abnormally: Segmentation fault: 11 > > Hmmm... > > To be honest, I think my ports area is a little scrambled right now, due > to some sort of a mistake when going to the new package system. Quite possibly > GDB is not much use, because PKG has been stripped (this is a binary-only > system). > > I guess it'll have to await my new server running FreeBSD 10 (I cannot > upgrade this one, as it's my only production box, and the hardware's days > are numbered). Have you tried deleting pkg, making sure you're grabbing the latest packages, and reinstalling pkg? a) pkg should not be segfaulting b) if you're not on the latest pkg version, the bug could have already been fixed ./koobs ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"