On 08/07/15 05:11, Kevin Oberman wrote:
> Isn't rebuilding the index useful for people running STABLE? I assume that
> I need a current index to get useful output from "pkg version -vL=". I am
> probably a bit unusual in that I keep a current ports tre on a STABLE
> system, but there are a couple o
On 08/07/15 09:40, Matthew Seaman wrote:
> Of course, if you're using custom options, then the ports tree you
the ports *INDEX*
D'Oh!
Matthew
signature.asc
Description: OpenPGP digital signature
FreeBSD_HEAD_i386 - Build #778 - Failure:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/778/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/778/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/778/console
Change summaries:
28641
Xin Li wrote:
> On 8/6/15 22:24, Kevin Oberman wrote:
> > Or the code in portsnap could be modified to get the current
> > running version.
>
> I thought about this today but it won't work as advertised: someone
> (currently me) still have to tweak the portsnap builder configuration
> to announce
Am Thu, 6 Aug 2015 18:13:55 +0300
Gleb Smirnoff schrieb:
> Hi!
>
> As part of the "opaque ifnet project" [1], all 802.11 (WiFi) drivers
> undergo change of not being an interface anymore. Historically in FreeBSD
> 802.11 stack, 802.11 devices called if_attach() and created an interface.
> La
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/07/15 08:50, Jamie Landeg-Jones wrote:
> Xin Li wrote:
>
>> On 8/6/15 22:24, Kevin Oberman wrote:
>>> Or the code in portsnap could be modified to get the current
>>> running version.
>>
>> I thought about this today but it won't work as ad
FreeBSD_HEAD_i386 - Build #779 - Still Failing:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/779/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/779/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/779/console
Change summaries:
Xin Li wrote:
> > I was going to suggest this too. Isn't this information available
> > using /bin/freebsd-version -u ?
>
> Client side: yes.
>
> Server side: someone has to tell the server to start building for new
> - -CURRENT or stop building for old -STABLE.
Ahhh! Gotcha! Thanks for the qui
FreeBSD_HEAD_i386 - Build #780 - Fixed:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/780/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/780/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/780/console
Change summaries:
286416
FreeBSD_HEAD - Build #3045 - Fixed:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD/3045/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD/3045/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD/3045/console
Change summaries:
286417 by marcel:
o Fi
Hi,
Gleb/others doing this: you have 4 days to figure out what's wrong
with things, or I'm backing all of this work out.
Thanks,
-adrian
On 7 August 2015 at 08:52, O. Hartmann wrote:
> Am Thu, 6 Aug 2015 18:13:55 +0300
> Gleb Smirnoff schrieb:
>
>> Hi!
>>
>> As part of the "opaque ifnet
Trying to debug TimeWarner IPV6 to my HE.NET tunnel, and running traceroute6,
got the following panic:
borg.lerctr.org dumped core - see /var/crash/vmcore.0
Fri Aug 7 19:58:40 CDT 2015
FreeBSD borg.lerctr.org 11.0-CURRENT FreeBSD 11.0-CURRENT #32 r286338: Wed Aug
5 15:57:55 CDT 2015 r...
is it easily reproducable for you there?
-a
On 7 August 2015 at 18:04, Larry Rosenman wrote:
> Trying to debug TimeWarner IPV6 to my HE.NET tunnel, and running traceroute6,
> got the following panic:
>
> borg.lerctr.org dumped core - see /var/crash/vmcore.0
>
> Fri Aug 7 19:58:40 CDT 2015
>
I got a 2nd one soon after just sitting -- I did JUST update sources,
turned off ipV6 to update (I seem to be having issues with TWC's IPV6).
Rebuild in process.
I **CAN** give you access to the cores, machine, et al.
I'd LOVE to figure out wtf is wrong on the IPV6 native stuff with TWC.
On
Of course as soon as I sent that I got another one..
On 2015-08-07 20:58, Larry Rosenman wrote:
just have the 2 panics. it doesn't "just reproduce".
I'll see what I can find.
Is there anything I can get for you from the core(s)?
On 2015-08-07 20:32, Larry Rosenman wrote:
I got a 2nd o
just have the 2 panics. it doesn't "just reproduce".
I'll see what I can find.
Is there anything I can get for you from the core(s)?
On 2015-08-07 20:32, Larry Rosenman wrote:
I got a 2nd one soon after just sitting -- I did JUST update sources,
turned off ipV6 to update (I seem to be having
Not always the same hop on the (slow) traceroute, but it DOES seem to
panic EVERY time.
On 2015-08-07 20:58, Larry Rosenman wrote:
Of course as soon as I sent that I got another one..
On 2015-08-07 20:58, Larry Rosenman wrote:
just have the 2 panics. it doesn't "just reproduce".
I'll
On Fri, Aug 07, 2015 at 08:04:01PM -0500, Larry Rosenman wrote:
> Trying to debug TimeWarner IPV6 to my HE.NET tunnel, and running traceroute6,
> got the following panic:
>
> borg.lerctr.org dumped core - see /var/crash/vmcore.0
>
> Fri Aug 7 19:58:40 CDT 2015
>
> FreeBSD borg.lerctr.org 11.0-
On 08/08/15 05:25, Mark Johnston wrote:
> On Fri, Aug 07, 2015 at 08:04:01PM -0500, Larry Rosenman wrote:
>> Trying to debug TimeWarner IPV6 to my HE.NET tunnel, and running
>> traceroute6,
>> got the following panic:
>>
>> borg.lerctr.org dumped core - see /var/crash/vmcore.0
>>
>> Fri Aug 7 19
19 matches
Mail list logo
