Date: Mon, 4 Nov 2013 19:18:09 +0100 From: Tijl Coosemans <tijl@FreeBSD.org> To: jerry@seibercom.net Cc: freebsd-ports@freebsd.org Subject: Re: Updating linux-f10-pango fails Message-ID: <20131104191809.4d89424c@kalimero.tijl.coosemans.org> In-Reply-To: <20131103173430.6a397cc9@scorpio> References: <20131015065816.4be007fb@scorpio> <CADL2u4hSVcaH2fDYJQ2=bj5RKCpRzyUE9GWbH1kNQO0paULuxg@mail.gmail.com> <525D3C65.7050501@passap.ru> <525E8715.9000205@freebsd.org> <20131016211703.00006ed9@unknown> <525EEEFB.6050403@FreeBSD.org> <20131103183004.6364bc18@kalimero.tijl.coosemans.org> <20131103230334.16b33efe@kalimero.tijl.coosemans.org> <20131103173430.6a397cc9@scorpio>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 3 Nov 2013 17:34:30 -0500 Jerry wrote:
> On Sun, 3 Nov 2013 23:03:34 +0100
> Tijl Coosemans articulated:
>>>> Am 16.10.2013 21:17, schrieb Alexander Leidinger:
>>>>> A normal install creates (or used to create, so at least there
>>>>> are old systems with this) the link /compat -> /usr/compat, so
>>>>> maybe somewhere realpath comes into use and exhibits a problem
>>>>> here ("here" being the staging support in general, not limited to
>>>>> the port).
>>
>> I've looked into this a bit deeper. The call to realpath in
>> pkg_create has been introduced in:
>> http://svnweb.freebsd.org/base?view=revision&revision=231300
>>
>> This revision has been MFCed to stable/8 between releng/8.3 and
>> releng/8.4 and to stable/9 between releng/9.0 and releng/9.1.
>>
>> The call has been disabled for absolute path names in
>> http://svnweb.freebsd.org/base?view=revision&revision=240682
>>
>> This revision has been MFCed to stable/8 between releng/8.3 and
>> releng/8.4 and to stable/9 between releng/9.1 and releng/9.2.
>>
>> So only FreeBSD 9.1 is affected by this.
>>
>> People in this thread running stable should just update. If you run
>> FreeBSD 9.1 a workaround is to switch to the new pkg tools.
>
> I can confirm that the build fails on FreeBSD 8.3.
>
> FreeBSD scorpio.seibercom.net 8.3-STABLE FreeBSD 8.3-STABLE #0: Fri Aug 17 13:52:14 EDT 2012 jerry@scorpio.seibercom.net:/usr/obj/usr/src/sys/SCORPIO amd64
The FreeBSD 8.3 release is not affected by this. After that release and
before the FreeBSD 8.4 release there's a window of about 6 months where
the bug exists. Your system is dated within that window so yes it is
affected, but updating it to FreeBSD 8.4 or latest 8-stable should fix it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131104191809.4d89424c>