[00:35] <wxl> s/kd
[00:35] <wxl> oops
[00:37] <wxl> so we have this little package that should create some .desktop files, btu it's failing because 'dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute' how to fix?
[00:42] <wgrant> wxl: It sounds like it's not actually creating any debs.
[00:42] <wgrant> That should be reproducible locally.
[00:43] <wxl> wgrant: i gather that, but why would that be?
[00:43] <wgrant> wxl: Your debian/rules or debian/control is wrong.
[00:44] <wxl> wgrant: control seems fine https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kubuntu-web-shortcuts/tree/debian/control
[00:44] <wxl> wgrant: and rules seems pretty simple, too https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kubuntu-web-shortcuts/tree/debian/rules
[00:45] <wgrant> wxl: How are you building it?
[00:46] <wxl> wgrant: to be fair, i haven't tried building it locally. i was expecting lp to take care of that for me :)
[00:46] <wgrant> wxl: Where's the build log?
[00:46] <wxl> did i not link that? sorry
[00:47] <wxl> wgrant: https://launchpadlibrarian.net/304799943/buildlog_ubuntu-zesty-amd64.kubuntu-web-shortcuts_17.04.0ubuntu1_BUILDING.txt.gz
[00:48] <wgrant> wxl: Your debian/rules is rather suspiciously missing a line that does something.
[00:49] <wgrant> It's not what you linked to in git.
[00:51] <wxl> it's not eh
[00:51] <wxl> this is what i get for trusting other people XD
[00:52] <wxl> hahahah yeah XD
[00:54] <wxl> thx wgrant
[00:54] <wgrant> np
[10:28] <rbasak> Could someone please take a look at https://answers.launchpad.net/launchpad/+question/426641? I don't mind it taking a while but it's frustrating having to keep reopening it.
[10:29] <rbasak> (it's about the git importer and ~ubuntu-branches)
[23:40] <bdmurray> wgrant: I'm curious about a build failure https://launchpadlibrarian.net/304937662/buildlog_ubuntu-zesty-armhf.apport-test-crashes_0.20170126-1~69~ubuntu17.04.1_BUILDING.txt.gz
[23:40] <bdmurray> wgrant: generate-crashes should be sending SIGSEGV not SIGILL
[23:41] <bdmurray> wgrant: http://bazaar.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/view/head:/generate-sigsegv-crash.py#L62
[23:42] <bdmurray> It works fine for me on rugby.
[23:52] <wgrant> bdmurray: You've tried it in an armhf chroot on rugby?
[23:53] <bdmurray> wgrant: yes, a zesty armhf chroot
[23:53] <wgrant> I agree the build log looks weird, but I'm interested if you've tried the same scenario.
[23:53] <wgrant> Huh
[23:53] <wgrant> (gdb) ERROR: apport (pid 8391) Thu Feb  2 23:30:19 2017: called for pid 8384, signal 11, core limit 0
[23:53] <wgrant> So it is getting segv, but gdb lies?
[23:57] <bdmurray> No, I think that's http://bazaar.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/view/head:/generate-sigsegv-crash.py#L74
[23:58] <bdmurray> So that message came from generate-sigsegv-crash.py
[23:58] <bdmurray> and the 11 is hard coded there