| === stub` is now known as stub | |
| [07:45] <ePierre> Hi everyone | |
| [08:59] <Odd_Bloke> Hello all. I'm hitting "No space left on device" when trying to build a binary image in a livefs. | |
| [08:59] <Odd_Bloke> https://launchpadlibrarian.net/192466114/buildlog_ubuntu_vivid_amd64_daniel-thewatkins-test_FAILEDTOBUILD.txt.gz is the buildlog in question. | |
| [09:01] <Odd_Bloke> I'm trying to build a ext4 disk image; I was building the image directly in the chroot stage, but live-build only supports disk labelling in the binary pass. | |
| [09:31] <wgrant> Odd_Bloke: Creating filesystem with 196351 4k blocks and 49152 inodes | |
| [09:31] <wgrant> That's 766MiB. | |
| [09:31] <wgrant> Is it conceivable that you're exceeding that size? | |
| [09:32] <Odd_Bloke> wgrant: It is conceivable, yes; though that's about the size I would expect the image to be. | |
| [09:35] <wgrant> Odd_Bloke: Perhaps tweak livecd-rootfs to create a bigger ext4 image. | |
| [09:36] <Odd_Bloke> wgrant: It looks like it's live-build that does that sizing; | |
| [09:36] <Odd_Bloke> Line 131 of lb_binary_hdd does a 'du -ms binary'. | |
| [09:37] <wgrant> Odd_Bloke: I know very little about livecd-rootfs, I'm afraid, but perhaps it underestimates the required image size for your case. | |
| [09:38] <wgrant> Consider hacking in a bit of a buffer to see if that works. | |
| [09:38] <Odd_Bloke> wgrant: Thanks for the pointer; will have a play around and see what I can do. :) | |
| [09:39] <wgrant> Let me know how it goes. | |
| [11:02] <Odd_Bloke> wgrant: Doubling the size of the disk has fixed the issue. | |
| [11:28] <Odd_Bloke> And after fixing another issue... Launchpad doesn't seem to have my binary HDD image as a built file. | |
| [11:28] * Odd_Bloke investigates. | |
| [11:29] <cjwatson> You basically just need to cause it to emit a non-symlink file whose name starts with "livecd." | |
| [11:29] <cjwatson> livecd-rootfs/live-build/auto/build does a bunch of copying to that end | |
| [12:52] <sergio-br2> hello | |
| [12:52] <sergio-br2> I'm having problem to build this package in launchpad | |
| [12:52] <sergio-br2> https://launchpadlibrarian.net/192654684/buildlog_ubuntu-trusty-armhf.libretro-gpsp_0.9%2Br200~3~ubuntu14.04.1_FAILEDTOBUILD.txt.gz | |
| [12:52] <sergio-br2> I can build it in one ARM board, but in launchpad it gets these can't resolve `.jit' {.jit section} errors | |
| === Guest58295 is now known as nesthib | |
| [14:08] <dobey> sergio-br2: have you tried building locally under qemu? | |
| [14:33] <sergio-br2> nope | |
| [14:37] <dobey> sergio-br2: first suggestion would be to try that. if you get the same problem, maybe there's a bug in qemu that's causing it | |
| [14:37] <sergio-br2> :/ | |
| [14:38] <sergio-br2> ok | |
| [14:38] * sergio-br2 needs to learn about qemu | |
| [14:38] <sergio-br2> if I build locally, and send with dput, launchpad build again or it only take the binary + source ? | |
| [14:39] <dobey> you can only upload source packages to launchpad, so yes, it will have to build again | |
| [14:42] <teward> are there any plans to let Debian builds into the PPAs, or is that still not a thing yet? | |
| [14:42] <teward> (at the very least i can spin up my own repo server for Debian builds, and build in `sbuild` schroots | |
| [14:42] <teward> so that's not as huge a priority, but I was wondering) | |
| [14:43] <dobey> i don't think it's being worked on yet | |
| [14:43] <teward> that's what i assumed - i was just curious :) | |