| Squidward | !ops | waaaaaaaaaaaa | 02:10 |
|---|---|---|
| ubot5 | waaaaaaaaaaaa: Help! lamont, zul, T-Bone, mdz, or jdub | 02:10 |
| === zyga is now known as zyga-afk | ||
| xnox | apw: where is instructions / procedures for setting up the meta tracking bugs for a kernel SRU release? | 11:22 |
| xnox | it's missing a step. | 11:22 |
| apw | xnox, you mean the release tracking bugs ? | 11:26 |
| xnox | apw: yeah. | 11:26 |
| apw | xnox, those are programatically generated .... | 11:26 |
| apw | xnox, what is missing from them ? | 11:26 |
| xnox | apw: excellent where is hte source code? | 11:26 |
| apw | xnox, ubuntu/kteam-tools | 11:26 |
| xnox | apw: it's missing "harass infinity to make a d-i upload to not have mismatched kernels on daily LTS image, which fails to boot, and qa team going crazy "OMG" the world is broke." | 11:27 |
| xnox | apw: or like do a d-i upload as part of kernel release. | 11:27 |
| apw | xnox, hmmm the source there is prolly not enough, as we need a new state for that prolly, as presumably there are two d-i's in that case? | 11:28 |
| apw | xnox, the real issue is whoever let it out of the SRU queue shouldn't have, without d-i, which should be britney guarded | 11:28 |
| apw | but ... that is cloud happy land | 11:28 |
| xnox | apw: what do you mean two d-i? it's one d-i that should be uploaded into -proposed and migrate into -updates together with kernel. | 11:28 |
| xnox | apw: britney is not run on SRUs, only on devel releases. | 11:29 |
| xnox | apw: thus even if there were packaging constraints they wouldn't help SRU at the moment, as far as I know. | 11:29 |
| * xnox checks | 11:29 | |
| apw | xnox, i know its not, i wish it was, so it would get stuck | 11:29 |
| apw | so that sru-release would be essentially an unblocka dd | 11:30 |
| xnox | apw: yeah that would be cool. | 11:30 |
| apw | xnox, but overall i think you are saying we need d-i tracking for it somehow ... and i think just saying that to bjf might make you cry less, than trying to read the code | 11:43 |
| xnox | apw: i think one simply needs a task open against ubuntu->d-i->series with indication that kernel version needs to be bumped | 11:44 |
| xnox | bjf: ^ | 11:44 |
| === zyga-afk is now known as zyga | ||
| AlbertoSN | Hello, my friends | 13:24 |
| AlbertoSN | It seems that, after a regular upgrade, the kernel no longer works with Radeon Evergreen graphics processors | 13:25 |
| AlbertoSN | https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397553 | 13:25 |
| ubot5 | Launchpad bug 1397553 in linux (Ubuntu) "The Linux kernel is no longer able to page the control register 2 in the Radeon Evergreen graphics processors, making the system to boot with a blank screen" [Critical,Triaged] | 13:25 |
| bjf | xnox, apw, you'd like another task on the tracking bugs? | 15:12 |
| xnox | bjf: yes. the task is "Upload d-i with kernel version bump" and is applicable for the default kernel flavour on all arches. | 15:13 |
| xnox | on all releases, both development and SRU. | 15:13 |
| bjf | xnox, if inifinity is ok with that then i'll add that to my todo list for shankbot & tracking bugs | 15:14 |
| xnox | bjf: in terms of ordering it should happen before kernels are migrated from -proposed -> -updates, as d-i should be promoted together with the kernel. | 15:14 |
| xnox | bjf: not sure about security uploads... probably d-i will be build and published /after/ security update is unembargoed. | 15:14 |
| bjf | xnox, ack | 15:14 |
| === kamal__ is now known as kamal | ||
| apw | infinity, yo ... where does the output of casper go, if it pukes errors on stderr, etc | 17:33 |
| infinity | apw: Not sure. | 18:04 |
| apw | i guess i get to try, if i can figure out how to test | 18:04 |
| simplify | Good afternoon everyone--where I am it is 15:37. I am attempting to compile a custom Ubuntu kernel the Debian way, but I get the same error every time. I even get this error when I compile the same kernel in a Ubuntu server VM.--and with the .config untouched! Every there I get this error! I don't understand this. I'll paste the error. It is four lines. BTW, I don't know how to set it so that the error messages are more verbose. *Also, I compiled the | 20:37 |
| simplify | kernel by following the directions at https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel* The "fakeroot debian/rules binary-headers binary-generic" command starts the compile. [I am pasting the four line error momentarily.] | 20:37 |
| simplify | > LD fs/built-in.o | 20:38 |
| simplify | > make[1]: *** [sub-make] Error 2 | 20:38 |
| simplify | > make[1]: Leaving directory `/usr/src/linux-3.13.0' | 20:38 |
| simplify | > make: *** [/usr/src/linux-3.13.0/debian/stamps/stamp-build-generic] Error 2 | 20:38 |
| simplify | I could use some help soon. | 20:40 |
| apw | simplify (N,BFTL), there would be a string starting "error:" some way before that which is the real error | 22:24 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!