search for: portbuild

Hi all, Is it mandatory to add device mem to jails to enable network via the gateway? Left ezjail with FreeBSD-6.3 (and a hardware replacement of my server) and am now starting again with FreeBSD-7.1. Early this week, I upgraded from 7.0 to 7.1 (not having 'used' jails on 7.0). After creating the jail with `ezjail-admin update -i` I created a 'ports build' jail `ezjail-admin

Updated my Athlon-xp 6-stable system last night, got an em watchdog timeout for the first time a few hours later, during a fairly high-traffic period. System is UP but does have device apic in the config. Any chance this is the recent race condition? Workaround? ifconfig em0 down, ifconfig em0 up seemed to cure it, at least for the moment. Thanks, Barney Wolff -- Barney Wolff I never

...dded 4 new committers, took in 1 commit bit for safe keeping, and re-instated 1 commit bit. In February, Mark Linimon (linimon) stepped down from his duties in the team. Mark had been the longest serving member of the team. Mark had spent many long hours refactoring and documenting the portbuild software to ensure that pointyhat services could be restored. After a security review, redports.org was turned back on, restoring Tinderbox services to contributors, along with post commit QATs. In addition, pointyhat infrastructure had also undergone a review and work begain on res...

...l/work/wine-1.3.8" && /usr/bin/make -j2 depend all " returned error 2 > :error:build Target org.macports.build returned: shell command failed > :debug:build Backtrace: shell command failed > while executing > "command_exec build" > (procedure "portbuild::build_main" line 8) > invoked from within > "$procedure $targetname" > :info:build Warning: the following items did not execute (for wine-devel): org.macports.activate org.macports.build org.macports.destroot org.macports.install > :notice:build Log for wine-devel is...