**** BEGIN LOGGING AT Thu Dec 29 03:00:00 2016 **** BEGIN LOGGING AT Thu Dec 29 16:57:07 2016 Dec 29 17:11:32 Anyone know offhand what generates localhost.crt in /usr/lib/ssl/certs? I'm guessing update-ca-certificates? Dec 29 17:13:41 for some reason it's ending up unreadable, funky perms Dec 29 17:23:09 kergoth: localhost.crt might be generated by a http server (nginx/apache/etc?) that is setup to serve a self-signed key, which could also explain the funky perms. I think it might be a bug if ca-certificates setup that file. Dec 29 17:29:17 no http server installed in this rootfs at all Dec 29 17:29:18 hmm Dec 29 17:31:15 kergoth: do you have this package https://pypi.python.org/pypi/ndg-httpsclient Dec 29 17:31:20 by chance ? Dec 29 17:31:35 nope Dec 29 17:31:55 we do have recipe for this in meta-python Dec 29 17:32:06 for both py2 and py3 Dec 29 17:32:18 those are potential providers for this file Dec 29 17:33:46 ah, good to know, thanks Dec 29 17:34:33 oh, shit, i think i know what's happening. this is during construction of an sdk-like thing — i bet for some reason the sdk conjversion of absolute to relative symlinks idn't happen Dec 29 17:34:44 then /usr/lib/ssl/certs would point to *host* /etc/ssl/certs Dec 29 17:34:46 * kergoth digs Dec 29 17:56:55 got it, sysroot-relativelinks.py only converts links to files or dead links. any links to directories on the host which exist will be left absolute. Dec 29 17:57:09 symlinks to dirs show up in 'dirs', not 'files' of an os.walk **** BEGIN LOGGING AT Thu Dec 29 18:01:37 2016 Dec 29 19:30:26 Hmm, qemu user mode is *not* happy with x32 binaries Dec 29 20:58:46 I love doing a devtool modify -x, realizing it wasn't a git recipe, adding the upstream git repo as a new remote, then grafting the tarball commit we used to the upstream tag :) **** ENDING LOGGING AT Fri Dec 30 03:00:00 2016