Re: net/libarcus fails to install

On Sun, Dec 27, 2020 at 2:41 PM Torfinn Ingolfsen wrote: > > net/libarcus builds, but fails to install: > root@kg-core2# make install > ===> Installing for libArcus-4.7.1_2,1 > ===> Checking if libArcus is already installed > ===> Registering installation for libArcus-4.7.1_2,1 > pkg-static:

INDEX now builds successfully on 11.x

___ 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"

INDEX build failed for 11.x

INDEX build failed with errors: Generating INDEX-11 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- --- describe.astro --- --- describe.audio --- --- describe.benchmarks --- --- describe.biology --- --- describe.cad --- --- describe.chinese --- ---

Re: Re-enabling old ciphers in openssl

On 2020-12-27 15:49, Dan Mahoney (Gushi) wrote: Ergo, I am wondering what the best way forward is to get a reasonably patched version of openssl that has old ciphers turned on (since it is still possible at compile-time, the code hasn't been outright removed), that I can build *some* subset of

How to fix/patch hardcoded values

Hello I've just submited a new port net/gitup and I used a simple workaround to help program find its config in /usr/local/etc instead of (hardcoded) ./ --- gitup.c.orig 2020-12-27 21:16:22 UTC +++ gitup.c @@ -2030,7 +2030,7 @@ main(int

Re-enabling old ciphers in openssl

Hey there all. This is a "don't try this at home" question. This is not something I'm asking how to do in the general case, but I'd like to know. It seems recently (since 1.1.1, OpenSSL has deprecated a number of ciphers, and made them a compile-time default disable.) WHat this means is

Re: How to fix/patch hardcoded values

In that case you might try an appropriate invocation of REINPLACE_CMD in post-patch. On 27/12/2020 22:58, Nuno Teixeira wrote: Hello I've just submited a new port net/gitup and I used a simple workaround to help program find its config

Re: Re-enabling old ciphers in openssl

On 12/27/20 4:49 PM, Dan Mahoney (Gushi) wrote: Hey there all. [...] Here are the questions I can't seem to answer: 1) There's no make.conf entry to override the openssl ciphers.  This needs to be done at the port level.  (Probably reasonable, I don't think there should be an insecure

Re: portmaster new development

Am 27.12.20 um 06:04 schrieb Thomas Mueller: And as portsnap user I have a question: Do they planning deprecation of portmaster too? No, I'm actively working on portmaster and have rewritten it from scratch for better performance (and additional features, e.g. building in a clean chroot

rubygem-rdoc upgrade breaks gitlab

Hi, I'm installing www/gimlab-ce, but a recent upgrade of rubygem-rdoc to 6.3 (rev 559245) breaks installation : # portinstall -v www/gitlab-ce [...] ===>   gitlab-ce-13.7.0 depends on package: rubygem-rdoc>=6.1.2<6.3 - not found *** Error code 1 Please note that requirement is *strictly*

Re: portmaster new development

Matthias Apitz wrote: > El día domingo, diciembre 27, 2020 a las 09:22:42a. m. +0100, Kurt Jaeger > escribió: >> That works as well. I have a checkout of the ports tree, use >> make config to define non-default port options. This stores the >> selected OPTIONs in /var/db/ports/, and poudriere

Re: portmaster new development

On Sun, 27 Dec 2020 11:16:23 +0100 Michael Grimm wrote: > Matthias Apitz wrote: > > El día domingo, diciembre 27, 2020 a las 09:22:42a. m. +0100, Kurt > > Jaeger escribió: > > >> That works as well. I have a checkout of the ports tree, use > >> make config to define non-default port options.

Re: portmaster new development

Hi! > How is poudriere in that regard? I never used poudriere, have been > intimidated by not wanting to use zfs or dialog4ports, or such an elaborate > setup just to update one or a few ports. poudriere is really, really useful. Because it delivers a complete, consistent package repo of all

Re: portmaster new development

On 27 Dec, Kurt Jaeger wrote: > Hi! > >> How is poudriere in that regard? I never used poudriere, have been >> intimidated by not wanting to use zfs or dialog4ports, or such an >> elaborate setup just to update one or a few ports. > > poudriere is really, really useful. Because it delivers a

Re: portmaster new development

El día domingo, diciembre 27, 2020 a las 09:22:42a. m. +0100, Kurt Jaeger escribió: > Hi! > > > How is poudriere in that regard? I never used poudriere, have been > > intimidated by not wanting to use zfs or dialog4ports, or such an elaborate > > setup just to update one or a few ports. > >

net/libarcus fails to install

net/libarcus builds, but fails to install: root@kg-core2# make install ===> Installing for libArcus-4.7.1_2,1 ===> Checking if libArcus is already installed ===> Registering installation for libArcus-4.7.1_2,1 pkg-static: Unable to access file

Re: portmaster new development

On Sat, Dec 26, 2020 at 07:23:59PM -0800, Thomas Mueller wrote: > ... An improved portmaster arouses my interest. Maybe modify the name so it > can be added to the ports tree and coexist with the "official" portmaster. > Desired features/options would be to keep going rather than stop when one