On Tue, 17 Apr 2012 17:27:11 +0200, Radek Polak wrote
> On Tuesday, April 17, 2012 03:00:54 PM Tiago Bortoletto Vaz wrote:
> 
> > I'm not sure which version I had in my freerunner before trying to update it
> > to v44. I'd suggest you to write next qtmoko version in /etc/issue{.net}
> > files as it's not a pure Debian chroot. So users will be able to easily
> > identify which is the current qtmoko version they have installed.
> 
> Hi,
> oki, like the idea. It seems that i have messed up with v44 kernel 
> version version, it's now 34 instead of 44.

Also, your linux-image postinst script checks if the /boot/uImage.bin file
exists and makes dpkg database broken for a fresh v44 ubi image:

root@neo:/media# apt-get -f install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up linux-image-2.6.34-qtmoko-gta02 (v44-1) ...
ln: creating symbolic link `/boot/uImage.bin': File exists
dpkg: error processing linux-image-2.6.34-qtmoko-gta02 (--configure):
 subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
                                      Errors were encountered while processing:
 linux-image-2.6.34-qtmoko-gta02
E: Sub-process /usr/bin/dpkg returned an error code (1)

You can fix this using "-L" rather than "-e" in the following code:

# Create the /boot/uImage.bin symlink
if [ "$1" = "configure" ]; then
    UBOOT_IMAGE=/boot/uImage.bin
    if [ ! -e "$UBOOT_IMAGE" ]; then
        cd /boot && ln -s uImage.bin-"$VERSION" "$UBOOT_IMAGE"
    fi
fi

Thanks for your work,

--
Tiago Bortoletto Vaz
http://tiagovaz.org
0xA504FECA - http://pgp.mit.edu


_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Reply via email to