Date: Wed, 23 Mar 2016 19:40:56 +0000 From: Glen Barber <gjb@FreeBSD.org> To: Marko Turk <markoml@markoturk.info> Cc: freebsd-pkgbase@freebsd.org Subject: Re: Missing METALOG Message-ID: <20160323194056.GI49119@FreeBSD.org> In-Reply-To: <20160323144318.GA1894@vps.markoturk.info> References: <56F169EC.6010400@pcbsd.org> <20160322164814.GJ58208@FreeBSD.org> <56F1979C.7010306@pcbsd.org> <20160322202242.GL58208@FreeBSD.org> <08F56E57-F9F4-4C3E-8154-108E5E50E3D0@ixsystems.com> <20160322210541.GM58208@FreeBSD.org> <20160323144318.GA1894@vps.markoturk.info>
next in thread | previous in thread | raw e-mail | index | archive | help
--FUFe+yI/t+r3nyH4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 23, 2016 at 03:43:18PM +0100, Marko Turk wrote: > it still doesn't work for me. I get the same error as before. >=20 > METALOG file contains some paths with MAKEOBJDIRPREFIX and some without > this. > For example: > ./bin type=3Ddir uname=3Droot gname=3Dwheel mode=3D0755 > ./boot type=3Ddir uname=3Droot gname=3Dwheel mode=3D0755 > ./boot/defaults type=3Ddir uname=3Droot gname=3Dwheel mode=3D0755 > ./boot/dtb type=3Ddir uname=3Droot gname=3Dwheel mode=3D0755 > ./boot/firmware type=3Ddir uname=3Droot gname=3Dwheel mode=3D0755 > ./boot/kernel type=3Ddir uname=3Droot gname=3Dwheel mode=3D0755 > [..cut..] > ./media/exports/freebsd-dev/obj//media/exports/freebsd-dev/src/i386.i386/= worldstage/sys type=3Dlink mode=3D0755 link=3Dusr/src/sys > ./media/exports/freebsd-dev/obj//media/exports/freebsd-dev/src/i386.i386/= worldstage/usr/share/man/en.ISO8859-1//man1 type=3Dlink mode=3D0755 link=3D= =2E./man1 > ./media/exports/freebsd-dev/obj//media/exports/freebsd-dev/src/i386.i386/= worldstage/usr/share/man/en.UTF-8//man1 type=3Dlink mode=3D0755 link=3D../m= an1 > [..cut..] >=20 > Is this maybe related to my problem? >=20 Yes, and this is bizarre. Can you please include the command history =66rom this attempt? I've spent several hours over the past few days looking into this, and want to make sure the same steps are reproduced while looking into the fix. Having said that, however, I will have limited access next week, so may not have a solution as quickly as we all would like. Glen --FUFe+yI/t+r3nyH4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJW8vFDAAoJEAMUWKVHj+KTMLMP/iA2jY/jX5t518XpT/99QLmO yQcmxXyynH+RUsiLq8ojYel0JZAKzLAkqwgqGSYO6CYHinbfq2TBIa1kMhvZNQUM 2UYmahpB79PpwStrRwAfT8n5+9ecsfDNwol8Er2BQpRzJEge8Kxw5OZdKnA5gwT6 oatqIT+J5duFEFzOGbLhy3KhPaNAAuHA0aqldHTb+FaQkTH56691pyCHOtdi0Yrf dl/pjaUdnWGA9Pu2bQt0AtpuihWTgM6gkHiMbpQexxp3Bq7RL6AQaXyn0kSHbXkT SaLGZsltrMWFFWAwrqNwZQ1QCm8FXYprkQ1DLcXo4zwWq0Gne3cvXKVuob1zYE+N n3aKoyup8epJ/VuA8MbzXRO30hMWco/Eos2cUZvbXNNGvvoO1nqEybXjpFeDaiAy JLG/bK4pc/V5O8zlD14lti7hX/iKLjGuIxLAKb+he0t4vCEdVPrUaHWxQ0Gvxo3J 79wpv0BytTznPdqahGe6CAPTE4PwrEzSre3TuFogbmJ9DXBKLuys+K7vvYmBebFZ WhReqm659AJkIKTth1fS+DCJQKFAYUx0lK6TnqotIPkh0Kb/YkkSqSYDcanV/0z3 7tmxnhO67ARDfFnDriWCxoAbmEfrp9qOBCc7HhR/q2oXCZfdvCyH5eOLGbSNZZ5O c9FsXeIJe6o4rsI3qETy =C/JV -----END PGP SIGNATURE----- --FUFe+yI/t+r3nyH4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160323194056.GI49119>