From owner-freebsd-ports@FreeBSD.ORG Wed Oct 16 19:54:38 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mandree.no-ip.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3752EE21; Wed, 16 Oct 2013 19:54:38 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 8A94E23CEEB; Wed, 16 Oct 2013 21:54:36 +0200 (CEST) Message-ID: <525EEEFB.6050403@FreeBSD.org> Date: Wed, 16 Oct 2013 21:54:35 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org, portmgr@FreeBSD.org Subject: Re: Updating linux-f10-pango fails References: <20131015065816.4be007fb@scorpio> <525D3C65.7050501@passap.ru> <525E8715.9000205@freebsd.org> <20131016211703.00006ed9@unknown> In-Reply-To: <20131016211703.00006ed9@unknown> X-Enigmail-Version: 1.5.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CTxUq4x5M34Fe4CafR0OAXNU3csMSUVxP" Cc: =?UTF-8?B?UmVuw6kgTGFkYW4=?= , jerry@seibercom.net X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Oct 2013 19:54:38 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --CTxUq4x5M34Fe4CafR0OAXNU3csMSUVxP Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am 16.10.2013 21:17, schrieb Alexander Leidinger: > On Wed, 16 Oct 2013 14:31:17 +0200 > Ren=C3=83=C2=A9 Ladan wrote: >=20 >> On 15-10-2013 15:00, Boris Samorodov wrote: >>> 15.10.2013 15:08, Ren=C3=A9 Ladan =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >=20 >>>> Here tar gets confused somehow, it wants to pack >>>> ${STAGEDIR}/usr/compat/linux (note the extra usr/ ), which fails >>>> consequently. >>> >>> Does the affected system (poudiere jail) use links, like >>> /compat -> /usr/compat? >>> >> Mine does not have a /usr/compat -> /compat link (nor the other way >> around), and /compat is only created when building/installing linux >> ports (or other ports that require it). >=20 > 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). >=20 > Bye, > Alexander. >=20 Alexander, I think I can confirm your assessment. Ren=C3=A9, I had the same issue as Jerry (as reported on IRC, on 9.1-RELEASE-amd64), but did not dig deeper. In the end I sidestepped the problem because I could not solve it; meaning I used poudriere to build the package and installed that through pkg_add. That is not the canonical way to do that. I think I can confirm Alexanders suspicion. I do have the symbolic link that Alexander states: $ ls -l /compat lrwxr-xr-x 1 root wheel 10 10 Okt 2009 /compat -> usr/compat "make package" in the actual system fails (poudriere is fine for me, too)= =2E So perhaps either Poudriere sets up the jail a touch differently than a regular system would install it (possibly through sysinstall or whatever I used to get 9.1, I do not remember). Now, my workaround that makes "make package" work is to alias the file systems instead of : # mv /compat /compat.off # mkdir /compat && mount_nullfs /usr/compat /compat (Further hints below.) Then: $ make package =3D=3D=3D> Building package for linux-f10-pango-1.28.3_1 Creating package /var/tmp/usr/ports.svn/x11-toolkits/linux-f10-pango/work/linux-f10-pango-= 1.28.3_1.tbz Registering depends: linux-f10-cairo-1.8.0_2 linux-f10-xorg-libs-7.4_1 linux-f10-fontconfig-2.6.0 linux-f10-expat-2.0.1 linux-f10-png-1.2.37_2 linux_base-f10-10_7. Registering conflicts: linux-pango-[0-9]* linux-f8-pango-[0-9]*. Creating bzip'd tar ball in '/var/tmp/usr/ports.svn/x11-toolkits/linux-f10-pango/work/linux-f10-pango= -1.28.3_1.tbz' $ *This would seem to confirm that the symlink is the trigger for the problem.* Now, for the archives, further hints: 1. to make the change permanent, add one line to /etc/fstab so the mount gets re-established after reboot # printf '/usr/compat\t\t/compat\t\tnullfs\trw\t\t0\t0\n' >> /etc/fstab 2. if instead you want to revert the change: # umount /compat # rmdir /compat && mv /compat.off /compat # sed -i.bak -e '/^\/usr\/compat/d' /etc/fstab 3. if /compat gets destroyed: # ln -sfn usr/compat /compat I hope portmgr can investigate and fix this problem. Best regards Matthias --CTxUq4x5M34Fe4CafR0OAXNU3csMSUVxP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJe7vwACgkQvmGDOQUufZVo9QCgkPTIX3QKJgM4xBVB8oy36Yf1 EUYAnjKnINw02Dv0hMBdFOIROirvyDoe =Spok -----END PGP SIGNATURE----- --CTxUq4x5M34Fe4CafR0OAXNU3csMSUVxP--