Re: update issue

On Sat, 6 Nov 2010 12:26:55 +0100 Istvan Galgand articulated: > Hi All, > > I regularly update my ports tree using portsnap fetch/update followed > by portmanager -u commands. (Not forgetting to check the content of > /usr/ports/UPDATING file.) It seems that some of the stuff > can't be downloa

update issue

Hi All, I regularly update my ports tree using portsnap fetch/update followed by portmanager -u commands. (Not forgetting to check the content of /usr/ports/UPDATING file.) It seems that some of the stuff can't be downloaded from the servers, so the update process is not finished successfully. I

Update Issue is with PAE, not SMP : A wee while ago, USB support on FreeBSD6.2 PAE systems was discouraged. Is that still the case?

If there are patches/updates to this issue I would REALLY like to know about them! :-) -- Brett Davidson Systems Engineer -- Net24 Limited Web: www.net24.co.nz Phone: 0800 5000 24 | DDI: +64 3 962 9518 -- // web hosting / email hosting / data backup // our reputation for reliability precedes us

Re: mod_perl update issue

Eric wrote: CPUTYPE?=athlon64 either way, its installed now. i have never seen that happen before. thanks! We all just found this when I submitted the 2.0.3 update. A patch will be added to the ports tree and I've committed a fix to mp2 svn upstream so 2.0.4 will not need it. Patch below (

Re: mod_perl update issue

Eric wrote: i am trying to upgrade my mod_perl to mod_perl2-2.0.2_1,3 and am getting the error below. I thought it might be related to ccache so i disabled it via NOCCACHE=yes but it still blew up at thr same spot. has anyone else seen this with this update or in the past that can offer a su

mod_perl update issue

i am trying to upgrade my mod_perl to mod_perl2-2.0.2_1,3 and am getting the error below. I thought it might be related to ccache so i disabled it via NOCCACHE=yes but it still blew up at thr same spot. has anyone else seen this with this update or in the past that can offer a suggestion? E