On Thu, Jul 12, 2012 at 08:03:09PM -0400, Jung-uk Kim wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 2012-07-12 14:04:58 -0400, Jung-uk Kim wrote:
> > OpenSSL 1.0.1c will be merged to head today. There will be
> > several important changes to note.
> >
> > - Several crypto/engin
Am 13.07.12 01:10, schrieb Doug Barton:
On 07/12/2012 03:02 PM, Baptiste Daroussin wrote:
On Thu, Jul 12, 2012 at 11:48:41AM -0700, Doug Barton wrote:
I do not mean this e-mail to be in any way critical. I was told after
the new OPTIONS framework discussion that I should have asked questions
be
Hello, Jung-uk.
You wrote 13 июля 2012 г., 4:03:09:
>> Therefore, all binaries depending on these need to be recompiled.
>> Also, you may have to merge your /etc/ssl/openssl.conf changes.
JuK> FYI, OpenSSL 1.0.1c import is complete now. Please let me know if you
JuK> have any problem.
No por
Hello, Lev.
You wrote 13 июля 2012 г., 12:29:03:
JuK>> FYI, OpenSSL 1.0.1c import is complete now. Please let me know if you
JuK>> have any problem.
LS> No ports with "USE_OPENSSL=yes" could be built now :( Ports system
LS> complains about not-installed base OpenSSL.
Sorry for noise, it is
On 07/12/2012 05:03 PM, Jung-uk Kim wrote:
> FYI, OpenSSL 1.0.1c import is complete now. Please let me know if you
> have any problem.
Sorry if I missed it, but did you bump OSVERSION for this change? If
not, could you? It would be helpful for dealing with ports stuff,
especially USE_OPENSSL.
Do
On 2012-Jul-11 15:32:47 -0700, Steve Kargl
wrote:
>I know an approach to implementing many of the missing
>functions.
Are you willing to share this insight so someone else could do the work?
> When I do find
>some free time, I look at what is missing and start to
>put together a new function.
What I want to know is this new pkg system going to remove the
requirement of having the complete ports tree on my system?
What I am looking for in an port system, is to install a port and any
files needed for the parent port and its dependents to automatically be
downloaded. So in the end my
Am 13.07.12 14:14, schrieb Fbsd8:
What I want to know is this new pkg system going to remove the
requirement of having the complete ports tree on my system?
What I am looking for in an port system, is to install a port and any
files needed for the parent port and its dependents to automaticall
On Friday, July 13, 2012 7:41:00 am Peter Jeremy wrote:
> AFAIK, none of the relevant standards (POSIX, IEEE754) have any
> precision requirements for functions other than +-*/ and sqrt() - all
> of which we have correctly implemented. I therefore believe that, for
> the remaining missing function
On Thursday, July 12, 2012 5:16:41 pm Doug Barton wrote:
> On 07/12/2012 02:11 PM, Craig Rodrigues wrote:
> > You might want to view Baptiste's pkgng presentation at BSDCan:
> >
> > http://www.youtube.com/watch?v=4Hxq7AHZ27I
>
> Sure, the next time I have an hour to spare.
>
> I don't think what
On 13/07/2012 13:14, Fbsd8 wrote:
> What I want to know is this new pkg system going to remove the
> requirement of having the complete ports tree on my system?
>
> What I am looking for in an port system, is to install a port and any
> files needed for the parent port and its dependents to automa
On 13 Jul 2012, at 13:18, John Baldwin wrote:
> On Friday, July 13, 2012 7:41:00 am Peter Jeremy wrote:
>> AFAIK, none of the relevant standards (POSIX, IEEE754) have any
>> precision requirements for functions other than +-*/ and sqrt() - all
>> of which we have correctly implemented. I therefor
Hi,
I know that this is not a very helpful information.
I have an Lenovo X220 running 10 from some 2 weeks ago. I just noticed that
the USB mouse (a wireless Logitech Trackman) becomes unusable when the
wireless (iwn) is not able to connect to the access point and a USB hard disk
is plugged in
On Fri, Jul 13, 2012 at 2:04 PM, Erich Dollansky
wrote:
> Hi,
>
> I know that this is not a very helpful information.
>
> I have an Lenovo X220 running 10 from some 2 weeks ago. I just noticed that
> the USB mouse (a wireless Logitech Trackman) becomes unusable when the
> wireless (iwn) is not abl
On 7/13/2012 3:16 AM, Michael Ranner wrote:
> I was also a bit concerned and reserved to pkgng. But I am also in
> contact with some local FreeBSD ports committers and one of them (decke)
> told me some stories about pkgng and poudriere. I saw the talk from Beat
> Gätzi (beat) at EU BSD Day 2012 ab
On Fri, Jul 13, 2012 at 09:41:00PM +1000, Peter Jeremy wrote:
> On 2012-Jul-11 15:32:47 -0700, Steve Kargl
> wrote:
> >I know an approach to implementing many of the missing
> >functions.
>
> Are you willing to share this insight so someone else could do the work?
For the missing trig and hyper
On Fri, Jul 13, 2012 at 01:53:39PM +0100, David Chisnall wrote:
> On 13 Jul 2012, at 13:18, John Baldwin wrote:
>
> > On Friday, July 13, 2012 7:41:00 am Peter Jeremy wrote:
> >> AFAIK, none of the relevant standards (POSIX, IEEE754) have any
> >> precision requirements for functions other than +-
On 07/13/2012 05:26 AM, John Baldwin wrote:
> On Thursday, July 12, 2012 5:16:41 pm Doug Barton wrote:
>> On 07/12/2012 02:11 PM, Craig Rodrigues wrote:
>>> You might want to view Baptiste's pkgng presentation at BSDCan:
>>>
>>> http://www.youtube.com/watch?v=4Hxq7AHZ27I
>>
>> Sure, the next time I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-13 05:55:04 -0400, Doug Barton wrote:
> On 07/12/2012 05:03 PM, Jung-uk Kim wrote:
>> FYI, OpenSSL 1.0.1c import is complete now. Please let me know
>> if you have any problem.
>
> Sorry if I missed it, but did you bump OSVERSION for this
On Fri, Jul 13, 2012, David Chisnall wrote:
> As do I. I'd also point out that the ONLY requirement for long
> double according to the standard is that it has at least the same
> precision as double. Therefore, any implementation of these
> functions that is no worse that the double version is co
On 7/13/2012 10:36 AM, Doug Barton wrote:
> On 07/13/2012 05:26 AM, John Baldwin wrote:
>> On Thursday, July 12, 2012 5:16:41 pm Doug Barton wrote:
>>> On 07/12/2012 02:11 PM, Craig Rodrigues wrote:
You might want to view Baptiste's pkgng presentation at BSDCan:
http://www.youtube.co
On 13 July 2012 17:02, Bryan Drewery wrote:
> On 7/13/2012 10:36 AM, Doug Barton wrote:
>> On 07/13/2012 05:26 AM, John Baldwin wrote:
>>> On Thursday, July 12, 2012 5:16:41 pm Doug Barton wrote:
On 07/12/2012 02:11 PM, Craig Rodrigues wrote:
> You might want to view Baptiste's pkgng pres
On 07/13/12 10:58, David Schultz wrote:
On Fri, Jul 13, 2012, David Chisnall wrote:
As do I. I'd also point out that the ONLY requirement for long
double according to the standard is that it has at least the same
precision as double. Therefore, any implementation of these
functions that is no
On Friday, July 13, 2012 11:36:11 am Doug Barton wrote:
> Also, please keep in mind that I was criticized for *not* speaking up
> about the OPTIONS changes, now I'm being criticized *for* speaking up
> prior to pkg going live. In spite of the fact that I'm doing my best to
> (repeatedly) be clear t
On 13 July 2012 09:07, Stephen Montgomery-Smith wrote:
> On 07/13/12 10:58, David Schultz wrote:
>>
>> On Fri, Jul 13, 2012, David Chisnall wrote:
>>>
>>> As do I. I'd also point out that the ONLY requirement for long
>>> double according to the standard is that it has at least the same
>>> preci
Just to jump back into the fray a bit, since this point hasn't been articulated
well.
On Jul 10, 2012, at 6:55 PM, Peter Jeremy wrote:
> On 2012-Jul-08 19:01:07 -0700, Steve Kargl
> wrote:
>> Well, on the most popular hardware (that being i386/amd64),
>> ld80 will use hardware fp instruction w
On Friday, July 13, 2012 11:58:05 am David Schultz wrote:
> On Fri, Jul 13, 2012, David Chisnall wrote:
> > As do I. I'd also point out that the ONLY requirement for long
> > double according to the standard is that it has at least the same
> > precision as double. Therefore, any implementation o
On 07/13/2012 08:52 AM, Jung-uk Kim wrote:
> On 2012-07-13 05:55:04 -0400, Doug Barton wrote:
>> On 07/12/2012 05:03 PM, Jung-uk Kim wrote:
>>> FYI, OpenSSL 1.0.1c import is complete now. Please let me know
>>> if you have any problem.
>
>> Sorry if I missed it, but did you bump OSVERSION for thi
On Thursday, July 12, 2012 1:51:20 pm John Baldwin wrote:
> On Thursday, July 12, 2012 12:37:13 pm Scott Long wrote:
> > Yup, this is a problem, and I like your fix; this kind of state is exactly
> > what
> > belongs in the map.
>
> Why don't I break out the fix first as a separate patch.
Here i
Hi,
On Thu, Jul 12, 2012 at 1:20 AM, Warner Losh wrote:
> [..]
> Honestly, though, I think you'll be more pissed when you find out that the
> N:1 interface that you want is being done in the wrong domain. But I've been
> wrong before and look forward to seeing your replacement.
>
I will just p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-13 04:00:14 -0400, Konstantin Belousov wrote:
> How did the asm files were generated (I am sure they are generated)
> ?
Yes, they are all re-generated. Mostly, it is described in
FREEBSD-upgrade file:
http://svnweb.freebsd.org/base/vendor
Will port also be MFCed to 9-RELENG and 9.1-RELEASE? Do not want to
have to go to -CURRENT to get latest OpenSSL.
--Brett Glass
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-13 15:03:39 -0400, Brett Glass wrote:
> Will port also be MFCed to 9-RELENG and 9.1-RELEASE? Do not want
> to have to go to -CURRENT to get latest OpenSSL.
Sorry, we have no plan to MFC this to stable branches because of API
and feature cha
On Fri, Jul 13, 2012 at 5:14 AM, Fbsd8 wrote:
> What I want to know is this new pkg system going to remove the requirement
> of having the complete ports tree on my system?
>
> What I am looking for in an port system, is to install a port and any files
> needed for the parent port and its dependen
Someone who has yet to confess added -Werror to the global CFLAGS
(via /etc/make.conf) for one of our systems at work. Before I
figured out that this was the cause of builds failing, I hacked up
pam_passwdc to resolve the problem. This gets the module to
WARNS=2, but to go farther, the "logically
On 2012-Jul-13 11:58:05 -0400, David Schultz wrote:
>I propose we set a timeframe for this, on the order of a few months.
...
>If the schedule can't be met, then we can just import Cephes as an
>interim solution without further ado. This provides Bruce and Steve
>an opportunity to commit what the
On Jul 13, 2012, at 4:38 PM, Peter Jeremy wrote:
> On 2012-Jul-13 11:58:05 -0400, David Schultz wrote:
>> I propose we set a timeframe for this, on the order of a few months.
> ...
>> If the schedule can't be met, then we can just import Cephes as an
>> interim solution without further ado. Thi
Hi,
On Friday, July 13, 2012 09:10:16 PM Bernhard Schmidt wrote:
> On Fri, Jul 13, 2012 at 2:04 PM, Erich Dollansky
>
> wrote:
> > Hi,
> >
> > I know that this is not a very helpful information.
> >
> > I have an Lenovo X220 running 10 from some 2 weeks ago. I just noticed
> > that the USB mou
Hello -current,
I'm [re-]announcing that (after much delay from the first announcement) that I
am finally importing bsdconfig(8) into HEAD. Here's what to expect from the
import:
1. The Makefile for usr.sbin will not automatically descend into the new
usr.sbin/bsdconfig directory.
2. To add b
On Sat, Jul 14, 2012 at 08:38:08AM +1000, Peter Jeremy wrote:
> On 2012-Jul-13 11:58:05 -0400, David Schultz wrote:
> >I propose we set a timeframe for this, on the order of a few months.
> ...
> >If the schedule can't be met, then we can just import Cephes as an
> >interim solution without furthe
On 14/07/2012, at 2:35, Eitan Adler wrote:
>>>
>>> If the schedule can't be met, then we can just import Cephes as an
>>> interim solution without further ado. This provides Bruce and Steve
>>> an opportunity to commit what they have been working on, without
>>> forcing the rest of the FreeBSD c
On Jul 2, 2012, at 6:24 PM, Devin Teske wrote:
>
> On Jun 30, 2012, at 3:47 PM, Bruce Cran wrote:
>
>> On 28/06/2012 00:11, Devin Teske wrote:
>>> I'd like to announce that I intend to import bsdconfig(8) today.
>>
>> I haven't seen this get committed yet - was there a problem?
>>
>
> No pro
It seems recent OpenSSL update broke fetch(1) for me.
$ diff -u $SRC_BASE/crypto/openssl/apps/openssl.cnf /etc/ssl/openssl.cnf
$ fetch https://foo/bar
fetch: https://foo/bar: Authentication error
Same error as with the patch for 1.0.0d from a year ago and
same workaround - s/SSLv23_client_m
TB --- 2012-07-14 03:14:06 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-07-14 03:14:06 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
TB --- 2012-07-14 04:10:08 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-07-14 04:10:08 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
45 matches
Mail list logo
