[00:32] ogra: vorlon: this is a newer image than the one I tested a few weeks ago? I'm at a sprint in Taipei right now btw, so my tz is different from the normal [00:35] plars: i'm not sure i remember your tz ever being normal :) [00:36] mwhudson: it's all a matter of perspective [01:35] plars: yes, this is newer, http://cdimage.ubuntu.com/ubuntu-core/16/stable/20181109.4/ [01:55] vorlon: I'm looking at it now. Do you know what all changed in it? I don't see a fix for the ethernet LED issue yet on rpi3b+, but I know that's not really a regression since 3b+ wasn't supported previously on 16 [01:56] plars: it should be the same as the previous image, just validating that the image still DTRT now that the snaps are promoted to stable === JanC_ is now known as JanC [10:47] Hi, I have an odd case and hope somebody might have a hint [10:48] I build in sbuild and it fails on dh_install [10:48] it complains about this [10:48] dh_install [10:48] cp: cannot open 'debian/tmp/usr/lib/x86_64-linux-gnu/libgps.so.24' for reading: Too many levels of symbolic links [10:48] dh_install: cp --reflink=auto -a debian/tmp/usr/lib/x86_64-linux-gnu/libgps.so.24 debian/tmp/usr/lib/x86_64-linux-gnu/libgps.so.24.0.0 debian/libgps24//usr/lib/x86_64-linux-gnu/ returned exit code 1 [10:48] but [10:48] it actually is not on insane symlinks [10:48] ls -laF debian/tmp/usr/lib/x86_64-linux-gnu/libgps.so* [10:48] lrwxrwxrwx 1 paelzer paelzer 16 Nov 16 09:48 debian/tmp/usr/lib/x86_64-linux-gnu/libgps.so -> libgps.so.24.0.0* [10:48] lrwxrwxrwx 1 paelzer paelzer 16 Nov 16 09:48 debian/tmp/usr/lib/x86_64-linux-gnu/libgps.so.24 -> libgps.so.24.0.0* [10:48] -rwxrwxr-x 1 paelzer paelzer 630408 Nov 16 09:48 debian/tmp/usr/lib/x86_64-linux-gnu/libgps.so.24.0.0* [10:48] and even more so, if I chroot into the build env and just do the copy command [10:48] then it works [10:49] anyone an idea what I might look for? [11:16] the same build (with the issue described above) works for cosmic, but fails for disco and debian-unstable [12:42] on the above issue with the so not able to be copied - it fails also in launchpad. But it behaves different per archietcture [12:42] ppc fails https://launchpadlibrarian.net/397834496/buildlog_ubuntu-disco-ppc64el.gpsd_3.18.1-1_BUILDING.txt.gz [12:42] s390x works https://launchpadlibrarian.net/397834398/buildlog_ubuntu-disco-s390x.gpsd_3.18.1-1_BUILDING.txt.gz [12:42] they build the same thing [12:42] the same args [12:43] why would one have a different symlink depth ?!? [12:43] ahasenack: I trade the review for your MP for a good idea here :-) [12:44] something related to usr-merge? [12:47] I was in the chroot, it works fine [12:47] it almost seems like a racy thing [12:47] that works soon after [12:48] I've thrown it into https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3522/+packages [12:48] soem work some fail [12:48] I'm tempted to believe that on rebuilds they might even work/fail differently [12:49] ahasenack: checked, no usrmerge symlink in that path [12:49] cpaelzer: link to a failed build? [12:50] https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3522/+build/15668073/+files/buildlog_ubuntu-disco-ppc64el.gpsd_3.18.1-1_BUILDING.txt.gz ? [12:50] (just got an email about that one) [12:52] cpaelzer: perhaps you will have to do some debugging builds. Like overriging dh_install and adding a ls -la to it, something like that [12:53] or what's that other command that shows all path components, I forgot its name [12:53] namei [12:56] ahasenack: yearh a good idea [12:57] ahasenack: I could also add a sync call to test my theory on too much FS laziness [12:57] also I did the review [12:58] thanks [13:01] suspicious that debian-testing and cosmic work [13:01] and the same in disco and unstable fai [13:01] l [13:01] unless my race has a love for making up its chances to set me on false tracks === fenris is now known as ejat [13:54] tianon: hi. there are now disco tars @ https://partner-images.canonical.com/core/disco/ [13:54] do you know when docker images will come? [15:17] hi, who to safely remove python2.7 from cosmic without removing dependencies ? [15:17] how* [15:22] err, if there are still things depending on it that you aren't happy to remove in turn, then you can't safely remove it [15:22] sort of the definition of dependencies :) [17:32] bug 1781529 is ready to be approved now I think - blocks mysql-5.7 migration now. [17:32] bug 1781529 in mecab (Ubuntu) "[MIR] mecab" [High,In progress] https://launchpad.net/bugs/1781529 [17:38] rbasak: promoting [18:18] Thanks! [18:19] vorlon: did you miss mecab-ipadic? [18:20] (difference source package, same upstream project, same bug) [18:24] rbasak: I didn't miss it, I don't see it listed on either http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed or http://people.canonical.com/~ubuntu-archive/component-mismatches [18:26] Oh [18:26] I'll look into that, sorry. [18:27] Skuggen: ^ do you remember where the dependency on mecab-ipadic should be coming from? [18:29] "mecab depends on mecab-ipadic. Other dependencies are in main" https://bugs.launchpad.net/ubuntu/+source/mecab/+bug/1781529 [18:29] Launchpad bug 1781529 in mecab-ipadic (Ubuntu) "[MIR] mecab" [Undecided,Fix committed] [20:17] Unit193: Where is the code for udevbot? [20:26] I just can't find where it's kept, hm. [20:26] Maybe internally at Canonical? [21:57] acheronuk: nice catch; mwhudson usually handles that but he's probably swamped on his other ever-increasing responsibilities so I've opened https://github.com/tianon/docker-brew-ubuntu-core/pull/139 to get the ball rolling