apw | infinity, ok found it ... | 00:17 |
---|---|---|
infinity | apw: \o/ | 00:20 |
apw | infinity, interface change in teh kernel, requires an fs-FOO alias .. | 00:23 |
apw | ali1234, pastebin the error and we might be able to help | 15:38 |
ali1234 | apw: i am having difficulty finding the actual error because the debian scripts hide the verbose output | 15:45 |
ali1234 | i have actually narrowed the problem down to the repository can only be built once, and then you have to clone it again | 15:46 |
apw | ali1234, shouln't be, i do that constyantly | 15:46 |
apw | ali1234, pastbin the whole failed build output | 15:46 |
ali1234 | ok, please wait 2 hours | 15:47 |
ali1234 | the weird thing is that i can clone the "broken" repo and then clone works once | 15:47 |
apw | ali1234, well its either hiding the output, or there is a lot of output, not both | 15:48 |
ali1234 | you have to wait 2 hours because it compiles for 2 hours and the fails | 15:48 |
apw | if you are not doing _anything_ other than dpkg-buildpackage in it then it should just work | 15:48 |
ali1234 | i'm not doing dpkg-buildpackage at all | 15:48 |
apw | if you are making it using make, then probabally rmdir include/config is going to fix it for you | 15:49 |
ali1234 | nope | 15:49 |
ali1234 | i'm doing: git clean -f -d -x (which restores respotiory to identical state as when it was cloned, confirmed with diff -ur) | 15:49 |
ali1234 | fakeroot debian/rules clean | 15:49 |
ali1234 | AUTOBUILD=1 fakeroot debian/rules binary-debs | 15:50 |
apw | ali1234, whit series you building | 15:56 |
ali1234 | raring | 15:56 |
apw | ali1234, will try same sequence, i assume you are saying if you run it twice in that exact order, the second fails | 16:12 |
ali1234 | correct | 16:13 |
ali1234 | i will spin up another vm and record the entire session... | 16:13 |
apw | ali1234, just did your pattern 2x here without issue | 16:34 |
ali1234 | in 20 minutes?? | 16:34 |
ali1234 | the full build takes over 2 hours for me on a quad core system | 16:34 |
apw | ali1234, it took longer cause we have network issues | 16:35 |
=== kentb-out is now known as kentb | ||
alex-s77 | Hi. I'd like to rebuild the kernel with one additional patch. At best, I'd like to end up with deb packages that I can install. How would I go about it? | 19:05 |
alex-s77 | do i need to put the patch file (with the diff) somewhere and tell the build system where the patch is, or how do you do that in Ubuntu? | 19:08 |
=== smb` is now known as smb | ||
apw | alex-s77, https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel | 19:16 |
apw | alex-s77, that is the current start of the art in building ones own | 19:17 |
alex-s77 | apw: thx. and how or where would I add the patch? or would I simply modify the source tree beforehand? | 19:18 |
apw | alex-s77, apply it with patch i guess | 19:18 |
alex-s77 | don't I need to tell dpkg (or whatever…) to run "patch …"? | 19:18 |
alex-s77 | or do I run patch manually? | 19:19 |
apw | alex-s77, you wuld need to apply the patch yourself | 19:19 |
alex-s77 | ah | 19:20 |
alex-s77 | apw: so it's not like RPM, where you tell the system what to do. | 19:20 |
ali1234 | i restarted the VM with 1 core to try to get better error messages and now i can't reproduce the problem | 19:52 |
ali1234 | (the do-over VM is still crunching on the first build) | 19:52 |
=== Traxer|32 is now known as Traxer|on | ||
apw | ali1234, i built it on a 24 way | 19:57 |
ali1234 | now i'm not sure if 1 core fixed it or rebooting fixed it :( | 19:58 |
ali1234 | or if it's just fooling me and it's going to crash out still | 19:58 |
=== smb` is now known as smb | ||
=== kentb is now known as kentb-out | ||
=== jibel_ is now known as jibel | ||
kimosabe | installed new kernel 3.9 in 13.04, but since restart unity is not working. Not even in the older kernel anymore... any suggestions? | 22:41 |
kimosabe | tried sudo apt-get install --reinstall ubuntu-desktop, but no good came of it... | 22:41 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!