Date: Thu, 17 Oct 2013 06:23:38 -0400 From: Jerry <jerry@seibercom.net> To: freebsd-ports@freebsd.org Subject: Re: Updating linux-f10-pango fails Message-ID: <20131017062338.6442fe67@scorpio> In-Reply-To: <525EEEFB.6050403@FreeBSD.org> References: <20131015065816.4be007fb@scorpio> <CADL2u4hSVcaH2fDYJQ2=bj5RKCpRzyUE9GWbH1kNQO0paULuxg@mail.gmail.com> <525D3C65.7050501@passap.ru> <525E8715.9000205@freebsd.org> <20131016211703.00006ed9@unknown> <525EEEFB.6050403@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/jD6NDzYN+JO9ByrJPfOjB21
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Wed, 16 Oct 2013 21:54:35 +0200
Matthias Andree articulated:
> Am 16.10.2013 21:17, schrieb Alexander Leidinger:
> > On Wed, 16 Oct 2013 14:31:17 +0200
> > Ren=C3=83=C2=A9 Ladan <rene@freebsd.org> 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
>=20
> Alexander,
>=20
> I think I can confirm your assessment.
>=20
>=20
> Ren=C3=A9,
>=20
> I had the same issue as Jerry (as reported on IRC, on
> 9.1-RELEASE-amd64), but did not dig deeper.
>=20
> 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.
>=20
> I think I can confirm Alexanders suspicion.
>=20
> I do have the symbolic link that Alexander states:
>=20
> $ ls -l /compat
> lrwxr-xr-x 1 root wheel 10 10 Okt 2009 /compat -> usr/compat
>=20
> "make package" in the actual system fails (poudriere is fine for me,
> too).
>=20
> 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).
>=20
>=20
> Now, my workaround that makes "make package" work is to alias the file
> systems instead of :
>=20
> # mv /compat /compat.off
> # mkdir /compat && mount_nullfs /usr/compat /compat
>=20
> (Further hints below.)
>=20
> Then:
>=20
> $ 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'
> $
>=20
> *This would seem to confirm that the symlink is the trigger for the
> problem.*
>=20
>=20
> Now, for the archives, further hints:
>=20
> 1. to make the change permanent, add one line to /etc/fstab so the
> mount gets re-established after reboot
>=20
> # printf '/usr/compat\t\t/compat\t\tnullfs\trw\t\t0\t0\n'
> >> /etc/fstab
>=20
> 2. if instead you want to revert the change:
>=20
> # umount /compat
> # rmdir /compat && mv /compat.off /compat
> # sed -i.bak -e '/^\/usr\/compat/d' /etc/fstab
>=20
> 3. if /compat gets destroyed:
>=20
> # ln -sfn usr/compat /compat
>=20
>=20
> I hope portmgr can investigate and fix this problem.
I asked the other day if I should file a PR against this port; however,
I never received a reply. Unless I am told not to, I will file one
tomorrow. I don't want this problem to fall through the cracks. Ever
since this staging support started, too many ports are failing. I am
wondering just how thoroughly this was tested before being force on the
general populace.
--=20
Jerry =E2=99=94
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________
--Sig_/jD6NDzYN+JO9ByrJPfOjB21
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)
iQEcBAEBAgAGBQJSX7q/AAoJEF2rWD2do7dNMtAH/15tVrBG0hO91o5On/aYO321
VsQzRYJFSt4kj9daxbXZp7igKOtypsUMzG7XCh/azI+xaQfw10VW3yAcFJ+3irGn
BKEOzvl4XuXl9z+LqhdhCrTZDNgBgteV+QyY8zalCEVRdlPex7pzzx2dxfzgiDg8
0l3oWlz2ZUYAGtjWcTs6dAsU5wKBa3+QXEqFP4rGj5cbQOpU6ql0jzemfwshMwxg
6XCvvjugAqeiPitNTsiVYf26wYpLWUTdSpvwRJZnWgtb6qcxgVF3r/gt72dph1yR
00gstIyHbL0lxzy/EFlBugxp5FwcgvfurF/okPVqTtEbhjPdWbQCfn6TonR0nHI=
=89QQ
-----END PGP SIGNATURE-----
--Sig_/jD6NDzYN+JO9ByrJPfOjB21--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131017062338.6442fe67>