date:20150404

Re: boostrapping pkg and ipv6

2015-04-04 Thread Marten

Hi all,

fyi:
pkg does not honor -4 or such config /usr/local/etc/pkg.conf
http://vuxml.freebsd.org/freebsd/vuln.xml.bz2 
 is not reachable over ipv6

adding ipv4 addresses in /etc/hosts are a workaround

data below,

kind regards,
Marten

on this box with ipv4 and 6 configured:

/usr/local/etc/pkg.conf   => IP_VERSION: 4

pkg -4 audit -F
pkg: http://vuxml.freebsd.org/freebsd/vuln.xml.bz2: 
 Operation timed out
pkg: cannot fetch vulnxml file


fetch http://vuxml.freebsd.org/freebsd/vuln.xml.bz2 

vuln.xml.bz2
fetch: transfer timed out

tcpdump shows no ipv4 traffic though is sees traffic to 
2001:1900:2254:206a::50:0


host  2001:1900:2254:206a::50:0
0.0.0.0.0.5.0.0.0.0.0.0.0.0.0.0.a.6.0.2.4.5.2.2.0.0.9.1.1.0.0.2.ip6.arpa domain 
name pointer wfe0.ysv.freebsd.org 

host vuxml.freebsd.org 
vuxml.freebsd.org  is an alias for 
wfe0.ysv.freebsd.org .
wfe0.ysv.freebsd.org  has address 8.8.178.110
wfe0.ysv.freebsd.org  has IPv6 address 
2001:1900:2254:206a::50:0
wfe0.ysv.freebsd.org  mail is handled by 0 .
2001:1900:2254:206a::50:0


while on another box without ipv6 configured:
fetch http://vuxml.freebsd.org/freebsd/vuln.xml.bz2 

vuln.xml.bz2  100% of  474 kB  434 kBps


adding the next line to /etc/hosts

8.8.178.110 vuxml.freebsd.org  wfe0.ysv.freebsd.org 



pkg -4 audit -F
pkg: vulnxml file up-to-date
0 problem(s) in the installed packages found.





> On Mar 28, 2015, at 9:10 AM, Marten  > wrote:
> 
> Hi all,
> 
> While bootstrapping pkg a fresh  jail on FreeBSD 10.1 with IPv6 enabled the 
> process stalls.
> 
> #uname -a
> FreeBSD node.vijn.org  10.1-RELEASE-p5 FreeBSD 
> 10.1-RELEASE-p5 #0: Tue Jan 27 08:55:07 UTC 2015 
> r...@amd64-builder.daemonology.net 
> :/usr/obj/usr/src/sys/GENERIC  
> amd64
> 
> -> /etc/jail.conf
> exec.start= "/bin/sh /etc/rc";
> exec.stop = "/bin/sh /etc/rc.shutdown";
> exec.clean;
> mount.devfs;
> path = "/data/jails/$name";
> 
> host.hostname="$name.vijn.org ";
> 
> node {
>   ip4.addr= 192.x.x.22;
>   ip6.addr= 2001:980::x::22;
>   }
> 
> 
> root@node:/ # ifconfig
> nfe0: flags=8843 metric 0 mtu 1500
>   options=8210b
>   ether 90:e6:ba:7a:44:e8
>   inet 192.x.x.22 netmask 0xff00 broadcast 192.x.x.255
>   inet6 2001:980::x::22 prefixlen 64
>   nd6 options=21
>   media: Ethernet autoselect (100baseTX )
>   status: active
> lo0: flags=8049 metric 0 mtu 16384
>   options=63
>   nd6 options=21
> 
> 
> root@http:/ # telnet pkg.freebsd.org  80
> Trying 2001:41c8:112:8300::50:1...
> Connected to pkg.freebsd.org .
> Escape character is '^]'.
> ^CConnection closed by foreign host.
> 
> 
> root@http:/ # pkg search node
> The package management tool is not yet installed on your system.
> Do you want to fetch and install it now? [y/N]: y
> Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/freebsd:10:x86:64/latest 
> http://pkg.FreeBSD.org/freebsd:10:x86:64/latest>, please wait...
> ^C
> 
> root@http:/ # pkg -4 search node
> The package management tool is not yet installed on your system.
> Do you want to fetch and install it now? [y/N]: y
> Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/freebsd:10:x86:64/latest 
> http://pkg.FreeBSD.org/freebsd:10:x86:64/latest>, please wait…
> ^C
> 
> disabling IPv6 in /etc/jail.conf
> node {
>   ip4.addr= 192.x.x.22;
> # ip6.addr= 2001:980::x::22;
>   }
> # /etc/rc.d/jail restart node
> 
> 
> # pkg search node
> The package management tool is not yet installed on your system.
> Do you want to fetch and install it now? [y/N]: y
> Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/freebsd:10:x86:64/latest 
> http://pkg.FreeBSD.org/freebsd:10:x86:64/latest>, please wait...
> Verifying signature with trusted certificate pkg.freebsd.org 
> .2013102301... done
> [node.vijn.org ] Installing pkg-1.4.12...
> [node.vijn.org ] Extracting pkg-1.4.12: 100%
> Message for pkg-1.4.12:
>  If you are upgrading from the old package format, first run:
> 
>   # pkg2ng
> drupal6-nodewords-6.x.1.14
> gstreamer-plugins-annodex-0.10.31_1,3
> leafnode-1.11.10_1
> monodevelop-5.0.1
> monodevelop-database-5.0.1
> munin-node-2.0.25_4
> node-0.12.0_1
> node-devel-0.11.16_1
> node-thrift-0.9.1_1
> node010-0.10.38
> p5-Tree-DAG_Node-1.25
> p5-Tree-Node-0.08_2
> p5-WebService-Linode-0.27

Re: boostrapping pkg and ipv6

2015-04-04 Thread Marten

Hi all,

fyi:
pkg does not honor -4 or such config /usr/local/etc/pkg.conf
http://vuxml.freebsd.org/freebsd/vuln.xml.bz2 
 is not reachable over ipv6

adding ipv4 addresses in /etc/hosts are a workaround

data below,

kind regards,
Marten

on this box with ipv4 and 6 configured:

/usr/local/etc/pkg.conf   => IP_VERSION: 4

pkg -4 audit -F
pkg: http://vuxml.freebsd.org/freebsd/vuln.xml.bz2: Operation timed out
pkg: cannot fetch vulnxml file


fetch http://vuxml.freebsd.org/freebsd/vuln.xml.bz2
vuln.xml.bz2
fetch: transfer timed out

tcpdump shows no ipv4 traffic though is sees traffic to 
2001:1900:2254:206a::50:0


host  2001:1900:2254:206a::50:0
0.0.0.0.0.5.0.0.0.0.0.0.0.0.0.0.a.6.0.2.4.5.2.2.0.0.9.1.1.0.0.2.ip6.arpa domain 
name pointer wfe0.ysv.freebsd.org

host vuxml.freebsd.org
vuxml.freebsd.org is an alias for wfe0.ysv.freebsd.org.
wfe0.ysv.freebsd.org has address 8.8.178.110
wfe0.ysv.freebsd.org has IPv6 address 2001:1900:2254:206a::50:0
wfe0.ysv.freebsd.org mail is handled by 0 .
2001:1900:2254:206a::50:0


while on another box without ipv6 configured:
fetch http://vuxml.freebsd.org/freebsd/vuln.xml.bz2
vuln.xml.bz2  100% of  474 kB  434 kBps


adding the next line to /etc/hosts

8.8.178.110 vuxml.freebsd.org wfe0.ysv.freebsd.org 



pkg -4 audit -F
pkg: vulnxml file up-to-date
0 problem(s) in the installed packages found.





> On Mar 28, 2015, at 9:10 AM, Marten  wrote:
> 
> Hi all,
> 
> While bootstrapping pkg a fresh  jail on FreeBSD 10.1 with IPv6 enabled the 
> process stalls.
> 
> #uname -a
> FreeBSD node.vijn.org  10.1-RELEASE-p5 FreeBSD 
> 10.1-RELEASE-p5 #0: Tue Jan 27 08:55:07 UTC 2015 
> r...@amd64-builder.daemonology.net 
> :/usr/obj/usr/src/sys/GENERIC  
> amd64
> 
> -> /etc/jail.conf
> exec.start= "/bin/sh /etc/rc";
> exec.stop = "/bin/sh /etc/rc.shutdown";
> exec.clean;
> mount.devfs;
> path = "/data/jails/$name";
> 
> host.hostname="$name.vijn.org ";
> 
> node {
>   ip4.addr= 192.x.x.22;
>   ip6.addr= 2001:980::x::22;
>   }
> 
> 
> root@node:/ # ifconfig
> nfe0: flags=8843 metric 0 mtu 1500
>   options=8210b
>   ether 90:e6:ba:7a:44:e8
>   inet 192.x.x.22 netmask 0xff00 broadcast 192.x.x.255
>   inet6 2001:980::x::22 prefixlen 64
>   nd6 options=21
>   media: Ethernet autoselect (100baseTX )
>   status: active
> lo0: flags=8049 metric 0 mtu 16384
>   options=63
>   nd6 options=21
> 
> 
> root@http:/ # telnet pkg.freebsd.org  80
> Trying 2001:41c8:112:8300::50:1...
> Connected to pkg.freebsd.org .
> Escape character is '^]'.
> ^CConnection closed by foreign host.
> 
> 
> root@http:/ # pkg search node
> The package management tool is not yet installed on your system.
> Do you want to fetch and install it now? [y/N]: y
> Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/freebsd:10:x86:64/latest 
> http://pkg.FreeBSD.org/freebsd:10:x86:64/latest>, please wait...
> ^C
> 
> root@http:/ # pkg -4 search node
> The package management tool is not yet installed on your system.
> Do you want to fetch and install it now? [y/N]: y
> Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/freebsd:10:x86:64/latest 
> http://pkg.FreeBSD.org/freebsd:10:x86:64/latest>, please wait…
> ^C
> 
> disabling IPv6 in /etc/jail.conf
> node {
>   ip4.addr= 192.x.x.22;
> # ip6.addr= 2001:980::x::22;
>   }
> # /etc/rc.d/jail restart node
> 
> 
> # pkg search node
> The package management tool is not yet installed on your system.
> Do you want to fetch and install it now? [y/N]: y
> Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/freebsd:10:x86:64/latest 
> http://pkg.FreeBSD.org/freebsd:10:x86:64/latest>, please wait...
> Verifying signature with trusted certificate pkg.freebsd.org 
> .2013102301... done
> [node.vijn.org ] Installing pkg-1.4.12...
> [node.vijn.org ] Extracting pkg-1.4.12: 100%
> Message for pkg-1.4.12:
>  If you are upgrading from the old package format, first run:
> 
>   # pkg2ng
> drupal6-nodewords-6.x.1.14
> gstreamer-plugins-annodex-0.10.31_1,3
> leafnode-1.11.10_1
> monodevelop-5.0.1
> monodevelop-database-5.0.1
> munin-node-2.0.25_4
> node-0.12.0_1
> node-devel-0.11.16_1
> node-thrift-0.9.1_1
> node010-0.10.38
> p5-Tree-DAG_Node-1.25
> p5-Tree-Node-0.08_2
> p5-WebService-Linode-0.27
> p5-XML-Node-0.11_1
> p5-XML-NodeFilter-0.01_1
> xnodecor-0.1_2
> 
> 
> -> enabling IPv6
> 
> #pkg search node
> drupal6-nodewords-6.x.1.14
> gstreamer-plugins-annodex-0.10.31_1,3
> leafnode-1.11.10_1
> monodevelop-5.0.1
> monodevelop-database-5.0.1
> munin-node-2.0.25_4
> node-0.12.0_1
> node-devel-0.11.16_1
> node-thrift-0.9.1_1
> node010-0.10.38
> p5-Tree-DAG_Node-1.25
> p5-Tree-Node-0.08_2
> p5-WebService-Lino

Re: boostrapping pkg and ipv6

2015-04-04 Thread Baptiste Daroussin

On Sat, Apr 04, 2015 at 10:02:04AM +0200, Marten wrote:
> Hi all,
> 
> fyi:
> pkg does not honor -4 or such config /usr/local/etc/pkg.conf
> http://vuxml.freebsd.org/freebsd/vuln.xml.bz2 
>  is not reachable over ipv6
> 
> adding ipv4 addresses in /etc/hosts are a workaround
> 
> data below,
> 
> kind regards,
> Marten
> 
> on this box with ipv4 and 6 configured:
> 
> /usr/local/etc/pkg.conf   => IP_VERSION: 4
> 
> pkg -4 audit -F
> pkg: http://vuxml.freebsd.org/freebsd/vuln.xml.bz2: Operation timed out
> pkg: cannot fetch vulnxml file
> 
> 
> fetch http://vuxml.freebsd.org/freebsd/vuln.xml.bz2
> vuln.xml.bz2
> fetch: transfer timed out
> 
> tcpdump shows no ipv4 traffic though is sees traffic to 
> 2001:1900:2254:206a::50:0
> 
> 
> host  2001:1900:2254:206a::50:0
> 0.0.0.0.0.5.0.0.0.0.0.0.0.0.0.0.a.6.0.2.4.5.2.2.0.0.9.1.1.0.0.2.ip6.arpa 
> domain name pointer wfe0.ysv.freebsd.org
> 
> host vuxml.freebsd.org
> vuxml.freebsd.org is an alias for wfe0.ysv.freebsd.org.
> wfe0.ysv.freebsd.org has address 8.8.178.110
> wfe0.ysv.freebsd.org has IPv6 address 2001:1900:2254:206a::50:0
> wfe0.ysv.freebsd.org mail is handled by 0 .
> 2001:1900:2254:206a::50:0
> 
> 
> while on another box without ipv6 configured:
> fetch http://vuxml.freebsd.org/freebsd/vuln.xml.bz2
> vuln.xml.bz2  100% of  474 kB  434 kBps
> 
> 
> adding the next line to /etc/hosts
> 
> 8.8.178.110 vuxml.freebsd.org wfe0.ysv.freebsd.org 
> 
> 
> 
> pkg -4 audit -F
> pkg: vulnxml file up-to-date
> 0 problem(s) in the installed packages found.
> 
Can you open a ticket on http://github.com/freebsd/pkg ?

Best regards,
Bapt


pgpFnZljdwxek.pgp
Description: PGP signature

GLIBCXX errors, a very few ports don't run

2015-04-04 Thread Jeffrey Bouquet


command: lnav -s
/usr/local/lib/gcc47/libstdc++.so.6: version GLIBCXX_3.4.20 required by 
/usr/local/bin/lnav not found

Script done on Sat Apr  4 04:56:17 2015


...
10.1-STABLE r280322
..
gcc-4.8...
gcc-ecj-4.5
gcc47-4.7...
gcc49-4.9...

Anyone know of the best practices to trim down/reconfigure the set of compilers 
one has installed so the
GLIBCXX/libstdc issue which sometimes appears goes away eventually, or is 
remedied by a libmap.conf ?
...
Or any similar fix?

Thanks.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: GLIBCXX errors, a very few ports don't run

2015-04-04 Thread Guido Falsi

On 04/04/15 14:11, Jeffrey Bouquet wrote:
> 
> command: lnav -s
> /usr/local/lib/gcc47/libstdc++.so.6: version GLIBCXX_3.4.20 required by 
> /usr/local/bin/lnav not found
> 
> Script done on Sat Apr  4 04:56:17 2015
> 
> 
> ...
> 10.1-STABLE r280322
> ..
> gcc-4.8...
> gcc-ecj-4.5
> gcc47-4.7...
> gcc49-4.9...
> 
> Anyone know of the best practices to trim down/reconfigure the set of 
> compilers one has installed so the
> GLIBCXX/libstdc issue which sometimes appears goes away eventually, or is 
> remedied by a libmap.conf ?
> ...
> Or any similar fix?

I have seen this happen in certain situations. It's the dynamic linker
which links them to the wrong libstdc++. In your case, it looks like you
have various gcc ports installed, so various libstdc++.

I think your best bet is removing all gcc ports and install just one
(the default one is 4.8, but you could choose to keep 4.9 if it works
fine for you) and reinstall any port missing libraries.

Using ports you can use "pkg check -Bn" to look for missing libraries
and rebuild such ports.

This should make them all use the available gcc version ad resolve the
conflict.

Hope this helps.

-- 
Guido Falsi 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Will ASAN MFC to 10-STABLE?

2015-04-04 Thread Kevin Bowling

I believe the last bits needed to try clang's ASAN feature is the 
clang-rt stuff.  Will this MFC with a clang 3.5 or 3.6 MFC?


Regards,
Kevin

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Will ASAN MFC to 10-STABLE?

2015-04-04 Thread Dimitry Andric

On 04 Apr 2015, at 23:30, Kevin Bowling  wrote:
> 
> I believe the last bits needed to try clang's ASAN feature is the clang-rt 
> stuff.  Will this MFC with a clang 3.5 or 3.6 MFC?

It depends on whether we will ever MFC the most recent version of clang
to stable/10.  Since clang 3.5.0 and later require C++11 support, doing
this will make it more difficult to upgrade from 9.x to 10.x, and not
everybody agrees that it is worth the trouble.

Once 9.x is EOL (expected at the end 2016), it might cease to be an
issue, though. :-)

-Dimitry

signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Will ASAN MFC to 10-STABLE?

2015-04-04 Thread Kevin Bowling


On 4/4/2015 3:11 PM, Dimitry Andric wrote:

On 04 Apr 2015, at 23:30, Kevin Bowling  wrote:


I believe the last bits needed to try clang's ASAN feature is the clang-rt 
stuff.  Will this MFC with a clang 3.5 or 3.6 MFC?


It depends on whether we will ever MFC the most recent version of clang
to stable/10.  Since clang 3.5.0 and later require C++11 support, doing
this will make it more difficult to upgrade from 9.x to 10.x, and not
everybody agrees that it is worth the trouble.

Once 9.x is EOL (expected at the end 2016), it might cease to be an
issue, though. :-)

-Dimitry


Do you know if the clang-rt stuff will function with clang 3.4 or were 
there changes in the compiler to accommodate FreeBSD?


Wondering if we could try and add just the clang-rt libraries since the 
end of 2016 is a long time away :)


Regards,
Kevin

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Will ASAN MFC to 10-STABLE?

2015-04-04 Thread Dimitry Andric

On 05 Apr 2015, at 00:19, Kevin Bowling  wrote:
> 
> On 4/4/2015 3:11 PM, Dimitry Andric wrote:
>> On 04 Apr 2015, at 23:30, Kevin Bowling  wrote:
>>> 
>>> I believe the last bits needed to try clang's ASAN feature is the clang-rt 
>>> stuff.  Will this MFC with a clang 3.5 or 3.6 MFC?
>> 
>> It depends on whether we will ever MFC the most recent version of clang
>> to stable/10.  Since clang 3.5.0 and later require C++11 support, doing
>> this will make it more difficult to upgrade from 9.x to 10.x, and not
>> everybody agrees that it is worth the trouble.
>> 
>> Once 9.x is EOL (expected at the end 2016), it might cease to be an
>> issue, though. :-)
>> 
>> -Dimitry
> 
> Do you know if the clang-rt stuff will function with clang 3.4 or were there 
> changes in the compiler to accommodate FreeBSD?

The sanitizer libraries are part of compiler-rt, and the version which
is compatible with clang 3.4 does not yet have full FreeBSD support.  I
don't think it is feasible to backport newer versions of these to
accommodate an older clang version.


> Wondering if we could try and add just the clang-rt libraries since the end 
> of 2016 is a long time away :)

No, that is not easily done.

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: pkgng cannot fetch from PACKAGESITE with nanobsd.sh in FreeBSD 10.1

2015-04-04 Thread Zenny

Hi again,

I appended the nanobsd configuration file with:

cust_NANOBSD_packages() {
env SSL_NO_VERIFY_HOSTNAME="true" \
env SSL_NO_VERIFY_PPER="true" \
pkg -c ${NANO_WORLDIR} install -fy ${PACKAGELIST}
env SSL_NO_VERIFY_HOSTNAME="true" \
SSL_NO_VERIFY_PEER="true" \
pkg -c ${NANO_WORLDDIR} clean -a -y
rm -f ${NANO_WORLDDIR}/var/db/pkg/repo-*.sqlite
}


But it keeps on saying that both -f and -y option for the package is
illegal as shown below:

+ cust_NANOBSD_packages
+ env SSL_NO_VERIFY_HOSTNAME=true env SSL_NO_VERIFY_PPER=true pkg -c
install -fy nano
pkg: illegal option -- f
pkg: illegal option -- y
pkg: chroot failed!

When I install with -y flag on the host node, it works fine, but
causing problem only in the chrooted environment. Where did I get
wrong? Thanks in advance.

Cheers,
/z

when I checked

On 4/3/15, Zenny  wrote:
> On 4/2/15, Baptiste Daroussin  wrote:
>> On Wed, Apr 01, 2015 at 12:48:21PM +0200, Zenny wrote:
>>> Hi,
>>>
>>> 1. In order to comply with the pkgng in FreeBSD 10.1, the following
>>> changes
>>> were appended to my customized nanobsd.conf:
>>>
>>> customize_cmd cust_NANOBSD_setup
>>> >
>>> > cust_NANOBSD_packages() {
>>> > chroot ${NANO_WORLDDIR} sh -c 'cd packages; pkg; pkg install nano; pkg
>>> > clean;'
>>> > }
>>> >
>>> > customize_cmd cust_NANOBSD_packages
>>> >
>>>
>>> Certainly I had tuned chrooted /etc/resolv.conf with:
>>>
>>> #tune resolv.conf
>>> > echo '
>>> > nameserver 8.8.8.8
>>> > nameserver 8.8.4.4
>>> > ' >> ${NANO_WORLDDIR}/etc/resolv.conf
>>> >
>>
>> This tuning is not needed you can specify the nameserver on pkg command
>> line:
>> pkg -o NAMESERVER="8.8.8.8" -c ${NANO_WORLDDIR} update
>
> Segmentation fault with above,
> + cust_NANOBSD_packages
> + pkg -o NAMESERVER=8.8.8.8 -c /usr/obj/nanobsd.NANOBSD//_.w update
> Child process pid=88756 terminated abnormally: Segmentation fault
>
> # dmesg | grep pkg   │
> pid 88756 (pkg), uid 0: exited on signal 11 (core dumped)
>
>>
>> You can also simply add NAMESERVER in your environement variable
>>>
>>> Still the package cannot be downloaded from PACKAGESITE and got built
>>> into
>>> nanobsd image.
>>>
>>> 2. Also tried with:
>>>
>>> cust_pkg() {
>>> > pkg -c ${NANO_WORLDDIR} update
>>> > pkg -c ${NANO_WORLDDIR} install nano
>>> > pkg -c ${NANO_WORLDDIR} clean
>>> > }
>>> >
>>> > customize_cmd cust_pkg
>>> >
>>>
>>> Both ways, I get the same error that reads as of below:
>>>
>>> cd: packages: No such file or directory
>>> > pkg: Error fetching
>>> > http://pkg.FreeBSD.org/freebsd:10:x86:64/latest/Latest/pkg.txz: No
>>> > address record
>>> > A pre-built version of pkg could not be found for your system.
>>> > Consider changing PACKAGESITE or installing it from ports:
>>> > 'ports-mgmt/pkg'.
>>> > The package management tool is not yet installed on your system.
>>> > Do you want to fetch and install it now? [y/N]: Bootstrapping pkg from
>>> > pkg+
>>> > http://pkg.FreeBSD.org/freebsd:10:x86:64/latest, please wait...
>>> > pkg: Error fetching
>>> > http://pkg.FreeBSD.org/freebsd:10:x86:64/latest/Latest/pkg.txz: No
>>> > address record
>>> > A pre-built version of pkg could not be found for your system.
>>> > Consider changing PACKAGESITE or installing it from ports:
>>> > 'ports-mgmt/pkg'.
>>> > The package management tool is not yet installed on your system.
>>> > Do you want to fetch and install it now? [y/N]: Bootstrapping pkg from
>>> > pkg+
>>> > http://pkg.FreeBSD.org/freebsd:10:x86:64/latest, please wait...
>>> > pkg: Error fetching
>>> > http://pkg.FreeBSD.org/freebsd:10:x86:64/latest/Latest/pkg.txz: No
>>> > address record
>>> > A pre-built version of pkg could not be found for your system.
>>> > Consider changing PACKAGESITE or installing it from ports:
>>> > 'ports-mgmt/pkg'.
>>> > The package management tool is not yet installed on your system.
>>> > Do you want to fetch and install it now? [y/N]: Bootstrapping pkg from
>>> > pkg+
>>> > http://pkg.FreeBSD.org/freebsd:10:x86:64/latest, please wait...
>>> >
>>>
>> Is pkg installed on your host? it seems not?
>>
>> Best regards,
>> Bapt
>>
>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkgng cannot fetch from PACKAGESITE with nanobsd.sh in FreeBSD 10.1

2015-04-04 Thread Brandon Allbery

On Sat, Apr 4, 2015 at 8:26 PM, Zenny  wrote:

> + cust_NANOBSD_packages
> + env SSL_NO_VERIFY_HOSTNAME=true env SSL_NO_VERIFY_PPER=true pkg -c
> install -fy nano
> pkg: illegal option -- f
> pkg: illegal option -- y
> pkg: chroot failed!
>
> When I install with -y flag on the host node, it works fine, but
> causing problem only in the chrooted environment. Where did I get
> wrong? Thanks in advance.
>

Notice that ${NANO_WORLDDIR} didn't substitute anything; it used "install"
as the chroot (which is why it failed) and -fy as global options instead of
options to the "install" command it didn't see because -c ate it.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkgng cannot fetch from PACKAGESITE with nanobsd.sh in FreeBSD 10.1

2015-04-04 Thread Zenny

Thanks Brandon.

Yes, I did notice a typo. Missed a 'D' in NANO_WORLDDIR:
pkg -c ${NANO_WORLDIR} install -fy ${PACKAGELIST}

/z


On 4/5/15, Brandon Allbery  wrote:
> On Sat, Apr 4, 2015 at 8:26 PM, Zenny  wrote:
>
>> + cust_NANOBSD_packages
>> + env SSL_NO_VERIFY_HOSTNAME=true env SSL_NO_VERIFY_PPER=true pkg -c
>> install -fy nano
>> pkg: illegal option -- f
>> pkg: illegal option -- y
>> pkg: chroot failed!
>>
>> When I install with -y flag on the host node, it works fine, but
>> causing problem only in the chrooted environment. Where did I get
>> wrong? Thanks in advance.
>>
>
> Notice that ${NANO_WORLDDIR} didn't substitute anything; it used "install"
> as the chroot (which is why it failed) and -fy as global options instead of
> options to the "install" command it didn't see because -c ate it.
>
> --
> brandon s allbery kf8nh   sine nomine
> associates
> allber...@gmail.com
> ballb...@sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad
> http://sinenomine.net
>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkgng cannot fetch from PACKAGESITE with nanobsd.sh in FreeBSD 10.1

2015-04-04 Thread Zenny

On 4/5/15, Zenny  wrote:
> Thanks Brandon.
>
> Yes, I did notice a typo. Missed a 'D' in NANO_WORLDDIR:
> pkg -c ${NANO_WORLDIR} install -fy ${PACKAGELIST}

The above asked to do a 'pkg update', so accordingly, I added to
custom_packages the following:

cust_NANOBSD_packages() {
env SSL_NO_VERIFY_HOSTNAME="true" \
env SSL_NO_VERIFY_PPER="true" \
pkg -c ${NANO_WORLDDIR} -f update
env SSL_NO_VERIFY_HOSTNAME="true" \
env SSL_NO_VERIFY_PPER="true" \
pkg -c ${NANO_WORLDDIR} install -y ${PACKAGELIST}
env SSL_NO_VERIFY_HOSTNAME="true" \
SSL_NO_VERIFY_PEER="true" \
pkg -c ${NANO_WORLDDIR} clean -a -y
rm -f ${NANO_WORLDDIR}/var/db/pkg/repo-*.sqlite
}

But it fails with:

+ env SSL_NO_VERIFY_HOSTNAME=true env SSL_NO_VERIFY_PPER=true pkg -c
/usr/obj/nanobsd.NANOBSD-PFS//_.w -f update
pkg: illegal option -- f
Updating FreeBSD repository catalogue...
pkg: http://pkg.FreeBSD.org/FreeBSD:10:amd64/latest/meta.txz: No address record
pkg: repository FreeBSD has no meta file, using default settings
pkg: http://pkg.FreeBSD.org/FreeBSD:10:amd64/latest/packagesite.txz:
No address record
pkg: Unable to update repository FreeBSD

h

>
> /z
>
>
> On 4/5/15, Brandon Allbery  wrote:
>> On Sat, Apr 4, 2015 at 8:26 PM, Zenny  wrote:
>>
>>> + cust_NANOBSD_packages
>>> + env SSL_NO_VERIFY_HOSTNAME=true env SSL_NO_VERIFY_PPER=true pkg -c
>>> install -fy nano
>>> pkg: illegal option -- f
>>> pkg: illegal option -- y
>>> pkg: chroot failed!
>>>
>>> When I install with -y flag on the host node, it works fine, but
>>> causing problem only in the chrooted environment. Where did I get
>>> wrong? Thanks in advance.
>>>
>>
>> Notice that ${NANO_WORLDDIR} didn't substitute anything; it used
>> "install"
>> as the chroot (which is why it failed) and -fy as global options instead
>> of
>> options to the "install" command it didn't see because -c ate it.
>>
>> --
>> brandon s allbery kf8nh   sine nomine
>> associates
>> allber...@gmail.com
>> ballb...@sinenomine.net
>> unix, openafs, kerberos, infrastructure, xmonad
>> http://sinenomine.net
>>
>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkgng cannot fetch from PACKAGESITE with nanobsd.sh in FreeBSD 10.1

2015-04-04 Thread Zenny

On 4/5/15, Zenny  wrote:
> On 4/5/15, Zenny  wrote:
>> Thanks Brandon.
>>
>> Yes, I did notice a typo. Missed a 'D' in NANO_WORLDDIR:
>> pkg -c ${NANO_WORLDIR} install -fy ${PACKAGELIST}
>
> The above asked to do a 'pkg update', so accordingly, I added to
> custom_packages the following:
>
> cust_NANOBSD_packages() {
> env SSL_NO_VERIFY_HOSTNAME="true" \
> env SSL_NO_VERIFY_PPER="true" \
> pkg -c ${NANO_WORLDDIR} -f update
> env SSL_NO_VERIFY_HOSTNAME="true" \
> env SSL_NO_VERIFY_PPER="true" \
> pkg -c ${NANO_WORLDDIR} install -y ${PACKAGELIST}
> env SSL_NO_VERIFY_HOSTNAME="true" \
> SSL_NO_VERIFY_PEER="true" \
> pkg -c ${NANO_WORLDDIR} clean -a -y
> rm -f ${NANO_WORLDDIR}/var/db/pkg/repo-*.sqlite
> }

It worked when I copied the /etc/resolv.conf to the ${NANO_WORLDDIR}.

cp /etc/resolv.conf ${NANO_WORLDDIR}/etc/


>
> But it fails with:
>
> + env SSL_NO_VERIFY_HOSTNAME=true env SSL_NO_VERIFY_PPER=true pkg -c
> /usr/obj/nanobsd.NANOBSD-PFS//_.w -f update
> pkg: illegal option -- f
> Updating FreeBSD repository catalogue...
> pkg: http://pkg.FreeBSD.org/FreeBSD:10:amd64/latest/meta.txz: No address
> record
> pkg: repository FreeBSD has no meta file, using default settings
> pkg: http://pkg.FreeBSD.org/FreeBSD:10:amd64/latest/packagesite.txz:
> No address record
> pkg: Unable to update repository FreeBSD
>
> h
>
>>
>> /z
>>
>>
>> On 4/5/15, Brandon Allbery  wrote:
>>> On Sat, Apr 4, 2015 at 8:26 PM, Zenny  wrote:
>>>
 + cust_NANOBSD_packages
 + env SSL_NO_VERIFY_HOSTNAME=true env SSL_NO_VERIFY_PPER=true pkg -c
 install -fy nano
 pkg: illegal option -- f
 pkg: illegal option -- y
 pkg: chroot failed!

 When I install with -y flag on the host node, it works fine, but
 causing problem only in the chrooted environment. Where did I get
 wrong? Thanks in advance.

>>>
>>> Notice that ${NANO_WORLDDIR} didn't substitute anything; it used
>>> "install"
>>> as the chroot (which is why it failed) and -fy as global options instead
>>> of
>>> options to the "install" command it didn't see because -c ate it.
>>>
>>> --
>>> brandon s allbery kf8nh   sine nomine
>>> associates
>>> allber...@gmail.com
>>> ballb...@sinenomine.net
>>> unix, openafs, kerberos, infrastructure, xmonad
>>> http://sinenomine.net
>>>
>>
>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Build failed in Jenkins: FreeBSD_stable_10 #1335

2015-04-04 Thread jenkins-admin

See 

Changes:

[kib] MFC r280342:
msdosfs: mark unused compat-mount fields.

[dim] MFC r272444 (by jkim):

  Merge ACPICA 20140926.

MFC r278970 (by jkim):

  Merge ACPICA 20141107 and 20150204.

Approved by:jkim
Relnotes:   yes

[kib] MFC r280797:
Make debug.vmem_check a tunable.  It is useful to set it early.

[kib] MFC r280323:
Somewhat modernize the SysV shm code.

MFC r280325 (by cognet):
Fix warning for !MAC case.

[kib] MFC r278697 (by alc):
Preset the object's color, or alignment, to maximize superpage usage.

[kib] MFC r258056 (by alc):
Eliminate the gratuitous use of mmap(2) flags from the implementation
of kern_shmat().  Use a simpler approach to determine whether to pass
VMFS_NO_SPACE or VMFS_OPTIMAL_SPACE to vm_map_find().

[bdrewery] MFC r280179,r280180:

  r280179:
Add LIB_CXX so that C++ libraries will use CXX to link.

This adds some extra dependencies directly to Makefile.inc1 as
atf is still a prebuild library in stable/10. If r273449 is MFCd
these can come out.

  r280180:
Document LIB and LIB_CXX.

[bdrewery] MFC r280870:

  Fix --one-file-system to include the directory encountered rather than
  excluding it.  This was broken in 3.0.4 (r238856).

Relnotes:   yes

[bdrewery] MFC r280178:

  Unhide linker line for libraries.

[bdrewery] MFC r280177:

  Remove unneeded handling of undefined NM.

[bdrewery] MFC r278600:

  Correct and clarify comment for __SMBF.

[bdrewery] MFC r278530:

  When catopen(3) returns an error, it caches the result of that error from
  r202992. The refcount on the cache entry is not initialized, so any attempt
  to clean the cache will skip over this item since it likely has a >0 value.

  This change is currently a NOP.

[bdrewery] MFC r272291:

  Document [EPERM] for UNIX sockets.

[alc] MFC r279720
  Correct a typo in vm_object_backing_scan() that originated in r254141.
  Specifically, change a lock acquire into a lock release.

--
[...truncated 50411 lines...]
--- obj ---
--- sbin.obj__D ---
/builds/FreeBSD_stable_10/obj/builds/FreeBSD_stable_10/sbin/pfctl created for 
/builds/FreeBSD_stable_10/sbin/pfctl
--- obj_subdir_pflogd ---
--- lib.obj__D ---
/builds/FreeBSD_stable_10/obj/builds/FreeBSD_stable_10/lib/clang/libllvmpowerpcinstprinter
 created for /builds/FreeBSD_stable_10/lib/clang/libllvmpowerpcinstprinter
--- sbin.obj__D ---
===> sbin/pflogd (obj)
--- lib.obj__D ---
--- obj_subdir_libllvmsparcasmparser ---
===> lib/clang/libllvmsparcasmparser (obj)
--- share.obj__D ---
--- obj ---
--- sys.obj__D ---
--- obj ---
/builds/FreeBSD_stable_10/obj/builds/FreeBSD_stable_10/sys/boot/i386/cdboot 
created for /builds/FreeBSD_stable_10/sys/boot/i386/cdboot
--- share.obj__D ---
/builds/FreeBSD_stable_10/obj/builds/FreeBSD_stable_10/share/doc/psd/26.rpcrfc 
created for /builds/FreeBSD_stable_10/share/doc/psd/26.rpcrfc
===> share/doc/psd/27.nfsrpc (obj)
--- sys.obj__D ---
===> sys/boot/i386/gptboot (obj)
--- sbin.obj__D ---
--- obj ---
--- lib.obj__D ---
--- obj ---
--- share.obj__D ---
--- obj ---
--- lib.obj__D ---
/builds/FreeBSD_stable_10/obj/builds/FreeBSD_stable_10/lib/clang/libllvmsparcasmparser
 created for /builds/FreeBSD_stable_10/lib/clang/libllvmsparcasmparser
--- sys.obj__D ---
--- obj ---
--- lib.obj__D ---
--- obj_subdir_libllvmsparccodegen ---
--- sbin.obj__D ---
/builds/FreeBSD_stable_10/obj/builds/FreeBSD_stable_10/sbin/pflogd created for 
/builds/FreeBSD_stable_10/sbin/pflogd
--- share.obj__D ---
/builds/FreeBSD_stable_10/obj/builds/FreeBSD_stable_10/share/doc/psd/27.nfsrpc 
created for /builds/FreeBSD_stable_10/share/doc/psd/27.nfsrpc
--- lib.obj__D ---
===> lib/clang/libllvmsparccodegen (obj)
--- sys.obj__D ---
/builds/FreeBSD_stable_10/obj/builds/FreeBSD_stable_10/sys/boot/i386/gptboot 
created for /builds/FreeBSD_stable_10/sys/boot/i386/gptboot
--- sbin.obj__D ---
--- obj_subdir_ping ---
--- sys.obj__D ---
===> sys/boot/i386/kgzldr (obj)
--- share.obj__D ---
===> share/doc/smm (obj)
--- sbin.obj__D ---
===> sbin/ping (obj)
--- share.obj__D ---
--- _sub.obj ---
===> share/doc/smm/title (obj)
--- sbin.obj__D ---
--- obj ---
--- sys.obj__D ---
--- obj ---
--- lib.obj__D ---
--- obj ---
--- sys.obj__D ---
/builds/FreeBSD_stable_10/obj/builds/FreeBSD_stable_10/sys/boot/i386/kgzldr 
created for /builds/FreeBSD_stable_10/sys/boot/i386/kgzldr
--- sbin.obj__D ---
/builds/FreeBSD_stable_10/obj/builds/FreeBSD_stable_10/sbin/ping created for 
/builds/FreeBSD_stable_10/sbin/ping
--- lib.obj__D ---
/builds/FreeBSD_stable_10/obj/builds/FreeBSD_stable_10/lib/clang/libllvmsparccodegen
 created for /builds/FreeBSD_stable_10/lib/clang/libllvmsparccodegen
--- sys.obj__D ---
===> sys/boot/i386/libi386 (obj)
--- lib.obj__D ---
--- obj_subdir_libllvmsparcdesc ---
--- sbin.obj__D ---
--- obj_subdir_ping6 ---
===> sbin/ping6 (obj)
--- lib.obj__D ---
===> lib/clang/libllvmsparcdesc (obj)
--- share.obj__D ---
--- obj ---
/builds/Free

Build failed in Jenkins: FreeBSD_stable_8 #244

2015-04-04 Thread jenkins-admin

See 

--
[...truncated 6591 lines...]
AUsys/dev/ep/if_epvar.h
AUsys/dev/ep/if_ep.c
AUsys/dev/ep/if_ep_mca.c
AUsys/dev/ep/if_ep_eisa.c
AUsys/dev/ep/if_epreg.h
A sys/dev/mvs
AUsys/dev/mvs/mvs_soc.c
AUsys/dev/mvs/mvs.h
AUsys/dev/mvs/mvs_if.m
AUsys/dev/mvs/mvs_pci.c
AUsys/dev/mvs/mvs.c
A sys/dev/spibus
AUsys/dev/spibus/spibus.c
AUsys/dev/spibus/spibus_if.m
AUsys/dev/spibus/spi.h
AUsys/dev/spibus/spibusvar.h
A sys/dev/ichsmb
AUsys/dev/ichsmb/ichsmb_pci.c
AUsys/dev/ichsmb/ichsmb_var.h
AUsys/dev/ichsmb/ichsmb.c
AUsys/dev/ichsmb/ichsmb_reg.h
A sys/dev/oce
AUsys/dev/oce/oce_sysctl.c
AUsys/dev/oce/oce_hw.h
AUsys/dev/oce/oce_if.h
AUsys/dev/oce/oce_queue.c
AUsys/dev/oce/oce_mbox.c
AUsys/dev/oce/oce_util.c
AUsys/dev/oce/oce_hw.c
AUsys/dev/oce/oce_if.c
A sys/dev/agp
AUsys/dev/agp/agp_ati.c
AUsys/dev/agp/agp_sis.c
AUsys/dev/agp/agpvar.h
AUsys/dev/agp/agp_via.c
AUsys/dev/agp/agp.c
AUsys/dev/agp/agp_amd.c
AUsys/dev/agp/agp_i810.c
AUsys/dev/agp/agpreg.h
AUsys/dev/agp/agp_ali.c
AUsys/dev/agp/agppriv.h
AUsys/dev/agp/agp_if.m
AUsys/dev/agp/agp_nvidia.c
AUsys/dev/agp/agp_amd64.c
AUsys/dev/agp/agp_intel.c
A sys/dev/siis
AUsys/dev/siis/siis.h
AUsys/dev/siis/siis.c
A sys/dev/scc
AUsys/dev/scc/scc_bfe_macio.c
AUsys/dev/scc/scc_dev_sab82532.c
AUsys/dev/scc/scc_dev_z8530.c
AUsys/dev/scc/scc_bfe_sbus.c
AUsys/dev/scc/scc_core.c
AUsys/dev/scc/scc_if.m
AUsys/dev/scc/scc_bfe_ebus.c
AUsys/dev/scc/scc_bus.h
AUsys/dev/scc/scc_bfe_quicc.c
AUsys/dev/scc/scc_bfe.h
AUsys/dev/scc/scc_dev_quicc.c
A sys/dev/mge
AUsys/dev/mge/if_mgevar.h
AUsys/dev/mge/if_mge.c
A sys/dev/et
AUsys/dev/et/if_etvar.h
AUsys/dev/et/if_et.c
AUsys/dev/et/if_etreg.h
A sys/dev/scd
AUsys/dev/scd/scd_isa.c
AUsys/dev/scd/scdvar.h
AUsys/dev/scd/scd.c
AUsys/dev/scd/scdreg.h
A sys/dev/pccbb
AUsys/dev/pccbb/pccbb_pci.c
AUsys/dev/pccbb/pccbb_isa.c
AUsys/dev/pccbb/pccbbvar.h
AUsys/dev/pccbb/pccbb.c
AUsys/dev/pccbb/pccbbdevid.h
AUsys/dev/pccbb/pccbbreg.h
A sys/dev/mn
AUsys/dev/mn/if_mn.c
A sys/dev/txp
AUsys/dev/txp/3c990img.h
AUsys/dev/txp/if_txp.c
AUsys/dev/txp/if_txpreg.h
A sys/dev/jme
AUsys/dev/jme/if_jmevar.h
AUsys/dev/jme/if_jme.c
AUsys/dev/jme/if_jmereg.h
A sys/dev/digi
AUsys/dev/digi/CX_PCI.c
AUsys/dev/digi/CX_PCI.bios.h
AUsys/dev/digi/digi_pci.c
AUsys/dev/digi/digi_isa.c
AUsys/dev/digi/Xr.fepos.h
AUsys/dev/digi/Xem.fepos.h
AUsys/dev/digi/CX.bios.h
AUsys/dev/digi/CX.c
AUsys/dev/digi/EPCX_PCI.fepos.h
AUsys/dev/digi/digi_pci.h
AUsys/dev/digi/digi.c
AUsys/dev/digi/Xe.bios.h
AUsys/dev/digi/Xe.c
AUsys/dev/digi/digireg.h
AUsys/dev/digi/EPCX.fepos.h
AUsys/dev/digi/digi_mod.h
AUsys/dev/digi/digi.h
AUsys/dev/digi/CX_PCI.fepos.h
AUsys/dev/digi/Xem.bios.h
AUsys/dev/digi/Xem.c
AUsys/dev/digi/Xr.bios.h
AUsys/dev/digi/Xr.c
AUsys/dev/digi/EPCX_PCI.c
AUsys/dev/digi/EPCX_PCI.bios.h
AUsys/dev/digi/CX.fepos.h
AUsys/dev/digi/Xe.fepos.h
AUsys/dev/digi/EPCX.c
AUsys/dev/digi/EPCX.bios.h
A sys/dev/ex
AUsys/dev/ex/if_ex_isa.c
AUsys/dev/ex/if_ex_pccard.c
AUsys/dev/ex/if_exvar.h
AUsys/dev/ex/if_ex.c
AUsys/dev/ex/if_exreg.h
A sys/dev/siba
AUsys/dev/siba/siba_cc.c
AUsys/dev/siba/siba_bwn.c
AUsys/dev/siba/siba_core.c
AUsys/dev/siba/siba_pcibvar.h
AUsys/dev/siba/siba_pcib.c
AUsys/dev/siba/sibavar.h
AUsys/dev/siba/siba.c
AUsys/dev/siba/sibareg.h
AUsys/dev/siba/siba_ids.h
A sys/dev/my
AUsys/dev/my/if_my.c
AUsys/dev/my/if_myreg.h
A sys/dev/fb
AUsys/dev/fb/vga.c
AUsys/dev/fb/vgareg.h
AUsys/dev/fb/machfb.c
AUsys/dev/fb/s3_pci.c
AUsys/dev/fb/gallant12x22.c
AUsys/dev/fb/machfbreg.h
AUsys/dev/fb/fb.c
AUsys/dev/fb/splash_bmp.c
AUsys/dev/fb/boot_font.c
AUsys/dev/fb/splash_txt.c
AUsys/dev/fb/fbreg.h
AUsys/dev/fb/splash.c
AUsys/dev/fb/splashreg.h
AUsys/dev/fb/vesa.c
AUsys/dev/fb/creator.c
AUsys/dev/fb/creatorreg.h
AU

Re: boostrapping pkg and ipv6

Re: boostrapping pkg and ipv6

Re: boostrapping pkg and ipv6

GLIBCXX errors, a very few ports don't run

Re: GLIBCXX errors, a very few ports don't run

Will ASAN MFC to 10-STABLE?

Re: Will ASAN MFC to 10-STABLE?

Re: Will ASAN MFC to 10-STABLE?

Re: Will ASAN MFC to 10-STABLE?

Re: pkgng cannot fetch from PACKAGESITE with nanobsd.sh in FreeBSD 10.1

Re: pkgng cannot fetch from PACKAGESITE with nanobsd.sh in FreeBSD 10.1

Re: pkgng cannot fetch from PACKAGESITE with nanobsd.sh in FreeBSD 10.1

Re: pkgng cannot fetch from PACKAGESITE with nanobsd.sh in FreeBSD 10.1

Re: pkgng cannot fetch from PACKAGESITE with nanobsd.sh in FreeBSD 10.1

Build failed in Jenkins: FreeBSD_stable_10 #1335

Build failed in Jenkins: FreeBSD_stable_8 #244

16 matches

Site Navigation

Mail list logo

Footer information