plugwash: do you have a document describing how to build/update the raspbian.org kernel and/or a (git) repo? * trumee (~trumee@c-73-155-84-209.hsd1.tx.comcast.net) has joined #raspbian * Intoxicated-Kcaj is now known as kcaj short answer: no it is at least a clear answer :-P longer answer: it depends if you are trying to update within an upstream major version or update to a newer upstream major version I want to try to update it to 4.1 to see whether some issues would be solved by upgrading from 3.18 to 4.1 * \\Mr_C\\ (mrc@71-91-134-81.dhcp.mtgm.al.charter.com) has joined #raspbian The former is normally relatively simple, there is a script at debian/update-rpi-patches which does most of the work. Unfortunately when I updated the rpi patches for the 3.18 kernel to the latest 3.18 code in the foundation tree it wouldn't see the SD card. * dougiel has quit (Remote host closed the connection) (kernel panic with initramfs and power led turns off during boot) I suspect i'm missing some kernel setting but I dunno what * babel has quit (Ping timeout: 246 seconds) And I'd like to play around to see whether I can find it ... and offer that as patches Note that I'm far from an expert, so the most likely outcome will be that I fail. But I'd like to give it a try Upgrading to a new upstream major version is a rather more involved process. * twolife` has quit (Ping timeout: 246 seconds) * babel (~quassel@2001:41d0:a:25b0::1) has joined #raspbian iirc when i've done it before it's gone something like 1: take the debdiff 2: filter out debian/patches using filterdiff * TheVoid has quit (Ping timeout: 246 seconds) 3: apply the filtered debdiff to a Debian source package for the correct major version 4: deal with any bits of the patch that failed to apply 5: update the settings in debian/update-rpi-patches 6: make debian/update-rpi-patches executable (since diff/patch don't preserve permissions) 7: run debian/update-rpi-patches * TheVoid (~thevoid@unaffiliated/thevoid) has joined #raspbian 8: try and work out what new config settings are needed from diffing the two major versions in the rpf repo, edit debian/config/armhf/config.rpi (I think that is the name, I may be misremembering) accordingly 9: hack away at the package until it builds successfully 10: build the package 11: test the kernel actually boots, if not hack on things some more until it does ok, thanks. That's going to be a challenge ;) lemme try and get you a link to my updated 3.18 package (the one where storage doesn't work) on what packages would you do the debdiff? On the 3.18 and 4.1 raspberrypi.org kernels? that would be great help :) If you are reffering to the debdiff in step 1 it's a debdiff between the raspbian kernel package and the debian kernel package it's based on * twolife` (~plop@loki.twolife.be) has joined #raspbian ah ok! (note: that list of steps was from memory, there may well be holes in it) I understand. But it's a whole lot more then I'd be able to come up with :) * fred1807 has quit (Quit: fred1807) ok, https://plugwash.raspbian.org/linux_3.18/linux-3.18_3.18.5-1~exp1%2brpi20.dsc thanks! feel free to download that and see if you can figure out why it isn't seeing the SD card. not seeing the SD card? That's kind of bad ;) If you are reffering to the debdiff in step 1 it's a debdiff between the raspbian kernel package and the debian kernel package it's based on <-- to further clarify when I say debdiff I mean source debdiff unless otherwise stated thanks for clarifying. It makes sense though, a diff on the source is probably more readable then one on a binary package i'm just saying that because debdiff has two very different functions one is to compare the file lists of two Debian binary packages, the other is to create a unified diff file between two Debian source packages. The latter is what we want (and frankly what most people using the tool want) but the former is the use the manpage emphasises I was just reading that manpage because I've never used debdiff before It's pretty simple, something like debdiff linux-3.18_3.18.5-1~exp1.dsc linux-3.18_3.18.5-1~exp1+rpi20.dsc > linux-3.18.debdiff * taza has quit () sorry are packages from experimental also stored on snapshot.d.o? (I guess I need that to get the debian sources) debdiff linux_3.18.5-1~exp1.dsc linux-3.18_3.18.5-1~exp1+rpi20.dsc > linux-3.18.debdiff yeah, you should be able to get linux_3.18.5-1~exp1.dsc from snapshot.debian.org you can also get it from https://sourcearchive.raspbian.org/main/l/linux/linux_3.18.5-1~exp1.dsc <--snip--> LOL it's a 16.5MB diff file * taza (~taza@unaffiliated/taza) has joined #raspbian * gbaman has quit (Ping timeout: 256 seconds) * TheLostAdmin has quit (Quit: Leaving) hence step 2 I'm also new to filterdiff. I tried 'filterdiff linux-3.18.debdiff > patch' but that generates (another) file of 16.5MB * morlenxus has quit (Ping timeout: 268 seconds) oh another thing, update-rpi-patches will run much faster if you have a clone of the rpi kernel tree in a directory called linuxgit in the parent of the directory where you have the package source extracted * Akex_ has quit (Quit: Connection closed for inactivity) filterdiff -p1 -x 'debian/patches/*' linux-3.18.debdiff > linux-3.18.debdiff.filtered thank you! I just tried "filterdiff -p1 -x 'linux_3.18.5-1~exp1.debian/debian/patches/*' linux-3.18.debdiff > linux-3.18.debdiff.filtered", but I'm still getting a 16.5MB file that was against debian's patches dir, but I got the same result against "linux-3.18_3.18.5-1~exp1+rpi20.debian/debian/patches/*" did you not try what I suggested? That was exactly what I tried, but I obviously missed something you seem to have added bits to what I suggested * jazzzu has quit (Ping timeout: 240 seconds) filterdiff -p1 -x 'debian/patches/*' linux-3.18.debdiff > linux-3.18.debdiff.filtered the p1 means that the match string is matched against the path with the first component stripped off I think I know what I did wrong go on......... I extracted linux_3.18.5-1~exp1.debian.tar.xz and thought that 'debian/patches/' was a reference into that extracted archive but the operation should be on only 1 file, namely the debdiff (itself) so it's something like grep, right? I guess for very loose definitions of "something like grep" yes the 'debian/patches/*' is a reference to file paths inside the diff (after the first component is stripped by -p1) now it's 1.3MB :) * rockstar__ (~rockstar@cpe-74-67-52-54.nycap.res.rr.com) has joined #raspbian