Re: OpenSSL multiple names?

2020-02-07 Thread Rainer Hurling
Am 08.02.20 um 00:01 schrieb LuKreme:
> On Feb 7, 2020, at 13:20, Rainer Hurling  wrote:
>>
>> Did you try
>>
>> 'portmaster -o security/openssl openssl111-1.1.1d'
> 
> Yes, that failed with no error. Trying to uninstall openssl111 said there was 
> no such port.

That could be because of an already deinstalled openssl111, if you tried
before with portmaster. In such cases, the reinstallation failed, but a
copy of the precedent installation is under
/usr/ports/packages/portmaster-backup ...

> 
>> (with DEFAULT_VERSIONS= ssl=openssl, instead ssl=openssl111)?
> 
> That was set back in January.
> 
>> For me, that worked.
> 
> pkg delete -f openssl111
> cd security/openssl 
> make install
> 
> That worked.

Nice to hear.
___
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: OpenSSL multiple names?

2020-02-07 Thread LuKreme
On Feb 7, 2020, at 13:20, Rainer Hurling  wrote:
> 
> Did you try
> 
> 'portmaster -o security/openssl openssl111-1.1.1d'

Yes, that failed with no error. Trying to uninstall openssl111 said there was 
no such port.

> (with DEFAULT_VERSIONS= ssl=openssl, instead ssl=openssl111)?

That was set back in January.

> For me, that worked.

pkg delete -f openssl111
cd security/openssl 
make install

That worked.


___
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: OpenSSL multiple names?

2020-02-07 Thread Rainer Hurling
Am 07.02.20 um 19:16 schrieb @lbutlr:
> On 07 Feb 2020, at 11:06, @lbutlr  wrote:
>>  I updated openssl in January, and as I said it has been recompiled several 
>> times 
> 
> To be clear, I did everything that UPDATING 20200101 mentions, including 
> reinstalling all ports, changing make.conf, etc.
> 
> But all along, the system has reported that the version is openssl111-1.1.1, 
> until 05 Feb. BTW, there is no new version of openssl listed in Postmaster 
> and the distill in security/openssl says the date is Wed Sep 11 02:04:23 MDT 
> 2019.
> 
>  root # cat security/openssl/distinfo
>  
> [11:14] [/usr/ports] 
> TIMESTAMP = 1568189063
> SHA256 (openssl-1.1.1d.tar.gz) = 
> 1e3a91bc1f9dfce01af26026f856e064eab4c8ee0a8f457b5ae30b40b8b711f2
> SIZE (openssl-1.1.1d.tar.gz) = 8845861
> 
> 
> 

Did you try

'portmaster -o security/openssl openssl111-1.1.1d'

(with DEFAULT_VERSIONS= ssl=openssl, instead ssl=openssl111)?

For me, that worked.
___
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: OpenSSL multiple names?

2020-02-07 Thread @lbutlr
On 07 Feb 2020, at 11:06, @lbutlr  wrote:
>  I updated openssl in January, and as I said it has been recompiled several 
> times 

To be clear, I did everything that UPDATING 20200101 mentions, including 
reinstalling all ports, changing make.conf, etc.

But all along, the system has reported that the version is openssl111-1.1.1, 
until 05 Feb. BTW, there is no new version of openssl listed in Postmaster and 
the distill in security/openssl says the date is Wed Sep 11 02:04:23 MDT 2019.

 root # cat security/openssl/distinfo  
   
[11:14] [/usr/ports] 
TIMESTAMP = 1568189063
SHA256 (openssl-1.1.1d.tar.gz) = 
1e3a91bc1f9dfce01af26026f856e064eab4c8ee0a8f457b5ae30b40b8b711f2
SIZE (openssl-1.1.1d.tar.gz) = 8845861



-- 
When this kiss is over it will start again But not be any different
could be exactly the same It's hard to imagine that nothing at
all Could be so exciting, could be this much fun


___
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: OpenSSL multiple names?

2020-02-07 Thread @lbutlr
On 06 Feb 2020, at 17:55, Koichiro Iwao  wrote:
> I think UPDATING 20200101 should help you.

Nope, that doesn’t help me. I updated openssl in January, and as I said it has 
been recompiled several times (well, at least six) since then as I have updated 
ports. This behavior of confusing the two forms “openssl-1.1.1d,1” and 
“openssl111-1.1.1f” is new.

> On Wed, Feb 05, 2020 at 06:41:19PM -0700, @lbutlr wrote:
>> When trying to port upgrade mariadb it reinstalled openssl (just about 
>> everything for the last month has reinstalled openssl)
>> 
>> I get this after a successful build
>> 
>> ===>   Registering installation for openssl-1.1.1d,1
>> Installing openssl-1.1.1d,1...
>> pkg-static: openssl-1.1.1d,1 conflicts with openssl111-1.1.1d
>> 
>> There is /usr/ports/security/openssl
>> 
>> So why are there two different formats on the port name and how do I fix 
>> this.


-- 
It was intended that when Newspeak had been adopted once and for all
and Oldspeak forgotten, a heretical thought...should be literally
unthinkable, at least so far as thought is dependent on words.


___
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: nss update again

2020-02-07 Thread Li-Wen Hsu
On Sat, Feb 8, 2020 at 12:20 AM ajtiM via freebsd-ports
 wrote:
> nss 3.49.2_1 built without problem but version 3.49.2_2 doesn't:

It seems we still cannot get rid ofMAKE_JOBS_UNSAFE=yes, I added it
back in r525491. Please check.
Sorry for the breakage and thanks for reporting.

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


nss update again

2020-02-07 Thread ajtiM via freebsd-ports
Hi!

nss 3.49.2_1 built without problem but version 3.49.2_2 doesn't:

File exists
gmake[4]: *** [../../coreconf/rules.mk:393:
FreeBSD12.1_OPT.OBJ/pathsub.o] Error 1 gmake[4]: *** Waiting for
unfinished jobs gmake[4]: Leaving directory
'/usr/ports/security/nss/work/nss-3.49.2/nss/coreconf/nsinstall'
gmake[3]: *** [../coreconf/rules.mk:101: libs] Error 2 gmake[3]:
Leaving directory
'/usr/ports/security/nss/work/nss-3.49.2/nss/coreconf' gmake[2]: ***
[coreconf/rules.mk:64: export] Error 2 gmake[2]: Leaving directory
'/usr/ports/security/nss/work/nss-3.49.2/nss' ===> Compilation failed
unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before
reporting the failure to the maintainer. *** Error code 1

Stop.
make[1]: stopped in /usr/ports/security/nss
*** Error code 1

Stop.
make: stopped in /usr/ports/security/nss

===>>> make build failed for security/nss
===>>> Aborting update

===>>> Update for security/nss failed
===>>> Aborting update

-- 
“In politics stupidity is not a handicap”. 

Napoleon Bonaparte
___
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: p5-Locale-Language?

2020-02-07 Thread Kurt Jaeger
Hi!

> How do I go about requesting a new Perl port for the Locale::Language
> module that was taken out of Perl 5.30? www/foswiki depends on that
> module and some of its functions have not worked since I upgraded
> the wiki system to 5.30. Since I use ports exclusively, I do not
> wish to revert to cpan to install such modules.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243956

has an update to the most recent version on CPAN for misc/p5-Locale-Codes

Let's see if the maintainer approves.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
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"