Thread: CSSU howto?
View Single Post
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#4
Originally Posted by maacruz View Post
One of my worries was the kernel packaging, because I build the package by hand, just putting together the binaries after a make, and thought we couldn't do a cssu until this were sorted (because the non-existent autobuilder).
Yeah, we should have a source package that builds and produces the same result predictably.

Of course, I'd prefer building the package with dpkg-buildpackage from sources, to have less chances of making a mistake, but I do not understand well how a multi-package build works (dpkg documentation is awful, isn't it?), and need for someone to explain it to me.
Did you look at the kernel-diablo package? That overlays kernel-source-diablo, patches it as appropriate and builds "normal"/debug/oprofile kernel binary packages as well as headers and modules.

Anyway, I'd start by putting the following packages into CSSU (testing for now):
bluez-utils_3.28-0osso7_armel.deb
dbus_1.0.2-0osso16_armel.deb
dbus-1-utils_1.0.2-0osso16_armel.deb
libdbus-1-3_1.0.2-0osso16_armel.deb
mini-rc_0.2.11-3_all.deb
gconf2_2.16.0-1osso15_armel.deb
libgconf2-6_2.16.0-1osso15_armel.deb
Just got around to having a look, sorry for the delay. We need a little bit of tidying up, ie make sure the Maintainer: field in debian/control is updated and that there is an up-to-date debian/changelog in each package.

We also need to put the .dsc & .changes files (and any diff.gz if present) in the repository, so if you could put those up in garage after rebuilding it'd be great :-)
 

The Following User Says Thank You to lma For This Useful Post: