| === sz0 is now known as sz0` | ||
| === sz0` is now known as sz0 | ||
| === adam_gone is now known as adam_g | ||
| === Guest98244 is now known as lag | ||
| === zequence_ is now known as zequence | ||
| * apw yawns | 07:47 | |
| RAOF | Time for the bees! | 07:49 |
|---|---|---|
| * RAOF will be able to deliver them in person next week. | 07:49 | |
| apw | oh bees yes please | 07:52 |
| === zequence is now known as GrumpyStudio | ||
| === GrumpyStudio is now known as zequence | ||
| === sz0 is now known as sz0` | ||
| === sz0` is now known as sz0 | ||
| kees | rtg: heads up on a kernel SRU patch: https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=754733ee8a82832b6dbd784facbe12dedd303f5e | 19:11 |
| kees | I'll have mdempsky open a bug and send the patch to the kernel-team list. | 19:11 |
| systest | how can I track which changes are incorporated in to the latest packages? specifically, I'm trying to determine if/when an upstream patch gets applied to fix https://lkml.org/lkml/2014/4/1/14 | 19:15 |
| === halfie_ is now known as halfie | ||
| bjf | systest, the "easiest" way is to look at our git repo | 20:05 |
| bjf | systest, that commit is in the trusty release version | 20:08 |
| systest | thanks, I'll clone a copy of the repo just to take a look. re being in the release version, thanks for looking that up | 20:10 |
| bjf | np | 20:10 |
| bjf | systest, in our trusty repo it's : f974c74cfa24b0872009d1cbab78f743c2535570 | 20:11 |
| systest | ty | 20:12 |
| === zequence_ is now known as zequence | ||
| infinity | install: cannot stat './tmp/generic_netboot/tree/lib/firmware/3.15.0-1-generic/device-tree/apm-mustang.dtb': No such file or directory | 21:09 |
| infinity | rtg: ^-- Did that move, or get dropped, or...? | 21:10 |
| rtg | infinity, its still there as far as I can tell. debian.master/rules.d/arm64.mk: dtb_files_generic += apm-mustang.dtb | 21:33 |
| infinity | The binary packages disagree with you. | 21:34 |
| rtg | hmm, checking. | 21:34 |
| infinity | Or, rather, my d-i build disagrees. Let me have a look at the binary packages. | 21:36 |
| rtg | firmware/3.15.0-1-generic/device-tree/apm-mustang.dtb | 21:36 |
| rtg | its in the linux-image package | 21:36 |
| rtg | infinity, the mustang firmware was never in a udeb. I wonder how dannf actually installs this beast. | 21:38 |
| infinity | rtg: It's not in the udeb anymore, and it used to be. | 21:39 |
| infinity | rtg: From trusty: http://paste.ubuntu.com/7490386/ | 21:39 |
| infinity | Though, a bit sketchy that the udeb doesn't contain *all* the same DTs that the linux-image deb contains. | 21:40 |
| infinity | Must have been some APM-specific hack there. | 21:40 |
| infinity | rtg: Note that on armhf, the kernel-image udeb appears to have all the DTs. | 21:41 |
| infinity | rtg: So, this is an arm64-specific oops. | 21:41 |
| rtg | infinity, dang, you're right. dunno what happened in the transition to utopic. I'll figure it out. | 21:41 |
| infinity | rtg: Ta. Whatever armhf does, that seems to be "the right thing to do" for arm64 too. | 21:41 |
| apw | rtg, well at least after the last upload its not a 'debian/*' issue as they diffed null | 21:42 |
| rtg | this line disappeared: debian.master/d-i/firmware/kernel-image:device-tree/apm-mustang.dtb ? | 21:42 |
| infinity | rtg: So, I'd argue the list should probably be expanded, but that's enough to make d-i happy, I think. | 21:43 |
| infinity | rtg: Since that's all that was shipped in trusty. | 21:43 |
| infinity | -rw-r--r-- root/root 4669 2014-05-18 19:33 ./lib/firmware/3.15.0-1-generic/device-tree/foundation-v8.dtb | 21:44 |
| infinity | -rw-r--r-- root/root 7782 2014-05-18 19:33 ./lib/firmware/3.15.0-1-generic/device-tree/rtsm_ve-aemv8a.dtb | 21:44 |
| infinity | -rw-r--r-- root/root 6985 2014-05-18 19:33 ./lib/firmware/3.15.0-1-generic/device-tree/apm-mustang.dtb | 21:44 |
| infinity | rtg: Those are the three that are in linux-image.deb, probably makes sense to mirror that to kernel-image.udeb. | 21:44 |
| infinity | rtg: And maybe to automate keeping them in sync too (I just noticed it's a manual list for armhf too, which seems crazy) | 21:44 |
| rtg | infinity, yup | 21:44 |
| infinity | rtg: But a quick turnaround of just the manual fix would do me for now if you'd like to see d-i build and your kernel migrate. :) | 21:44 |
| rtg | infinity, gimme a bit | 21:45 |
| hallyn | hm, migration/[0-3] are taking up a combined 90% cpu time | 21:53 |
| hallyn | though it's probably my punishment for cp'ing a large file on btrfs | 21:53 |
| infinity | rtg: Let me know when you're uploading, so I can give you sagari for ppc. | 22:06 |
| rtg | infinity, fire in the hole | 22:13 |
| infinity | rtg: Ta. I'm doing a test build of d-i PPC to see if I have more things to yell about, but I think my failure there was just the removal of e500. I hope. :P | 22:14 |
| infinity | And look at that, you got sagari without my help. | 22:15 |
| rtg | luck of the draw | 22:15 |
| infinity | rtg: Nice commit message. :P | 22:17 |
| rtg | infinity, keep it sime, don't confuse people | 22:17 |
| rtg | simple* | 22:17 |
| infinity | rtg: You could have just shortened that to "WTF?" | 22:17 |
| rtg | infinity, I think what happened is that APM got added during the trusty dev cycle after the utopic repo was opened and I forgot to forward port all of the mustang build bits. | 22:18 |
| infinity | Curse rebases and the lack of useful history. :/ | 22:19 |
| infinity | 'git log debian.master/d-i/firmware/kernel-image' is the most useless thing ever. | 22:19 |
| infinity | Anyhow, I guess that will be building all evening on armhf, so I'll get you a d-i upload late tonight. | 22:21 |
| rtg | infinity, thanks | 22:22 |
| infinity | rtg: Had to fix three other arches anyway. :P | 22:22 |
| infinity | rtg: I had 4 failing failing arches for 3 different reasons, I suspect this is a new record for me. | 22:23 |
| rtg | infinity, kind of sucks to be you | 22:23 |
| infinity | Sure does. | 22:23 |
| * rtg goes back to reefing on a power supply.... | 22:23 | |
| infinity | You shouldn't smoke those. | 22:24 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!