Re: 12-CURRENT won't configure to download packagesite.txz yet
On February 7, 2017 2:35:16 AM GMT+01:00, Jeffrey Bouquet
wrote:
>All the files
>
>/etc/FreeBSD.conf
>/usr/local/etc/pkg/repos/FreeBSD.conf
>/usr/local/etc/pkg.conf
>
>I edit time after time for
>{$ABI} which gives FreeBSD:11:i386 but I am on 12-CURRENT i386
>Anytime I try to attune to
>freebsd:12:x86:32or
>FreeBSD:12:i386 ...
>it downloads the packagesite again, as it does in the ABI example, but
>a terse
>error of wrong architecture, etc, and a fail to do anything to upgrade
>to Pkg-12.
>
>Can the proper file be rename upstream to what its architecture in
>simpler terms:
>like packagesite-i386-12.txz and a message printed upon de-TXZ the file
>so that
>the proper nomenclature is given to put into each of those three files
>above
>so that the generic packagesite.txz will not error out upon download?
>Or, put the instructions in /usr/src/UPDATING ?? since it is part of
>base?
>
>
>Or some other way to de-showstopper this v11 April 2016 CURRENT to v12
>Feb 2017 CURRENT
>upgrade which still has failed to enable seamonkey-2.46_5 to run
>non-segfault [ ie cannot run ]
>vs seamonkey-2.46_4 which four days ago ran without EVER segfaulting??
>And cannot build
>from ports for obscure .h clang-header file related reasons?
>___
>freebsd-current@freebsd.org mailing list
>https://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to
>"freebsd-current-unsubscr...@freebsd.org"
Please provide the output of:
uname -a
uname -K
uname -U
--
Allan Jude
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
12-CURRENT won't configure to download packagesite.txz yet
All the files
/etc/FreeBSD.conf
/usr/local/etc/pkg/repos/FreeBSD.conf
/usr/local/etc/pkg.conf
I edit time after time for
{$ABI} which gives FreeBSD:11:i386 but I am on 12-CURRENT i386
Anytime I try to attune to
freebsd:12:x86:32or
FreeBSD:12:i386 ...
it downloads the packagesite again, as it does in the ABI example, but a terse
error of wrong architecture, etc, and a fail to do anything to upgrade to
Pkg-12.
Can the proper file be rename upstream to what its architecture in simpler
terms:
like packagesite-i386-12.txz and a message printed upon de-TXZ the file so that
the proper nomenclature is given to put into each of those three files above
so that the generic packagesite.txz will not error out upon download?
Or, put the instructions in /usr/src/UPDATING ?? since it is part of base?
Or some other way to de-showstopper this v11 April 2016 CURRENT to v12 Feb 2017
CURRENT
upgrade which still has failed to enable seamonkey-2.46_5 to run non-segfault [
ie cannot run ]
vs seamonkey-2.46_4 which four days ago ran without EVER segfaulting?? And
cannot build
from ports for obscure .h clang-header file related reasons?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Seamonkey update
On Sun, 5 Feb 2017 20:05:51 -0500, roberth...@rcn.com wrote:
>
> Jeffrey Bouquet writes:
>
> > pkg today updated seamonkey, now it segfaults,
> > every which way I try to run it.
>
> I am running SeaMonkey 2.46_5 (compiled today) under:
>
> FreeBSD 11.0-RC2 #0 r304729: Wed Aug 24 06:59:03 UTC 2016 amd64
>
> .
> So far, indistinguishable from _4.
>
>
>
> Respectfully,
>
>
> Robert Huff
More progress but not so encouraging.
Rebuilt the machine on which seamonkey segfaulted, to v12-CURRENT
..
seamonkey still segfaults
after _4 _5 [ a showstopper for the v11 OR v12 desktop on that disk ]
/usr/bin/cc segfaults, prohibiting port building
after installworld [ a showstopper for v12 on that disk ]
pkg -vv reports v11
FreeBSD.conf
containing FreeBSD:12:x86:32,
containing /${ABI}/,
containing FreeBSD:12:i386
each error out in some manner or another, making package not usable.
[a showstopper for pkg usage on that disk ]
Firefox prohibits 2 entry anywhere, so I cannot log into the forums as
jb_fvwm2 on the newer machine to inquire there, not use most any
search query containing the numeric digit(s) 2 and at least two others.
[ a showstopper for firefox usage on that disk ]
.
None of these 4 problems were present on Feb 4 vs by the morning of today Feb
6...
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [RFC/RFT] projects/ipsec
On 06.02.2017 16:27, peter.b...@bsd4all.org wrote: Andrey, Is this going to MFC'ed to stable-11 in the future? I have tested with current and found no issues, but I would like to add it to a semi-production environment running stable-11 Hi, I thought to make MFC after a month or two, but I didn't seen any information when 11.1-RELEASE is planned. So, I don't know when feature freeze begins. Also there are some changes that can be considered as POLA violation, especially the single name space for SPI can affect some users. -- WBR, Andrey V. Elsukov ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [RFC/RFT] projects/ipsec
Andrey, Is this going to MFC'ed to stable-11 in the future? I have tested with current and found no issues, but I would like to add it to a semi-production environment running stable-11 Peter > On 6 Feb 2017, at 10:07, Andrey V. Elsukov wrote: > > On 11.12.2016 02:07, Andrey V. Elsukov wrote: >> I am pleased to announce that projects/ipsec, that I started several >> months ago is ready for testing and review. >> The main goals were: >> * rework locking to make IPsec code more friendly for concurrent >>processing; >> * make lookup in SADB/SPDB faster; >> * revise PFKEY implementation, remove stale code, make it closer >>to RFC; >> * implement IPsec VTI (virtual tunneling interface); >> * make IPsec code loadable as kernel module. > > JFYI, the project was merged into head/ in r313330. > > -- > WBR, Andrey V. Elsukov > ___ > freebsd-...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [RFC/RFT] projects/ipsec
On 11.12.2016 02:07, Andrey V. Elsukov wrote: I am pleased to announce that projects/ipsec, that I started several months ago is ready for testing and review. The main goals were: * rework locking to make IPsec code more friendly for concurrent processing; * make lookup in SADB/SPDB faster; * revise PFKEY implementation, remove stale code, make it closer to RFC; * implement IPsec VTI (virtual tunneling interface); * make IPsec code loadable as kernel module. JFYI, the project was merged into head/ in r313330. -- WBR, Andrey V. Elsukov ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
