Topic: opkg update failure

When I try to do an "opkg update" on the NeTV (following the instructions on the Wiki to install the local development tools), I get this:

root@localhost:~# opkg update
Downloading http://buildbot.chumby.com.sg/build/sil … ckages.gz.
Inflating http://buildbot.chumby.com.sg/build/sil … ckages.gz.
Updated list of available packages in /var/lib/opkg/sdk.
Downloading http://buildbot.chumby.com.sg/build/sil … kages.sig.
Signature check failed.
Remove wrong Signature file.
Downloading http://buildbot.chumby.com.sg/build/sil … ckages.gz.
Inflating http://buildbot.chumby.com.sg/build/sil … ckages.gz.
Updated list of available packages in /var/lib/opkg/local-all.
Downloading http://buildbot.chumby.com.sg/build/sil … kages.sig.
Signature check failed.
Remove wrong Signature file.
Downloading http://buildbot.chumby.com.sg/build/sil … ckages.gz.
Inflating http://buildbot.chumby.com.sg/build/sil … ckages.gz.
Updated list of available packages in /var/lib/opkg/local-armv5te.
Downloading http://buildbot.chumby.com.sg/build/sil … kages.sig.
Signature check failed.
Remove wrong Signature file.
Downloading http://buildbot.chumby.com.sg/build/sil … ckages.gz.
Inflating http://buildbot.chumby.com.sg/build/sil … ckages.gz.
Updated list of available packages in /var/lib/opkg/local-chumby-silvermoon-netv.
Downloading http://buildbot.chumby.com.sg/build/sil … kages.sig.
Signature check failed.
Remove wrong Signature file.

There's nothing int he /var/lib/opkg folder other than an empty "tmp" folder. Any ideas how to fix this?

Thanks,
Razvan

Re: opkg update failure

Yep, this is a known issue. We are reworking the update script and as such the signature doesn't match the update script. That's intentional, we don't want you to get an update that's in the process of being fixed.

We should have it resolved in the next couple of days.

7BAA 2E53 01C1 DCFF 497B  E7F0 9699 A303 78F0 D9B9

Re: opkg update failure

should be fixed now. Again, the update to 11 is not so exciting, just some minor bug fixes. Another update with more user-facing changes is coming in the next couple of days.

7BAA 2E53 01C1 DCFF 497B  E7F0 9699 A303 78F0 D9B9

Re: opkg update failure

It appears to be fixed, thank you! It also appears to have autoupdated to firmware version 11.

However, following the procedure at http://wiki.chumby.com/index.php/NeTV_local_compilation only freed up some 224 MB on the root partition, so I'm wondering if there's a list of the packages that are actually used by the current firmware. I would like to remove some non-essential packages (for instance Perl or Qt4 altogether) but other packages appear to depend on them. Is there anything in the current firmware that needs Qt or Perl (see below for output)? I would like to keep the current firmware functionality but free up enough space for GCC and associated tools.

Any suggestions?

Razvan

-------------------

root@localhost:~# opkg remove perl
No packages removed.
Collected errors:
* print_dependents_warning: Package perl is depended upon by packages:
* print_dependents_warning:     task-chumby-support
* print_dependents_warning:     cpi
* print_dependents_warning:     task-chumby-netv
* print_dependents_warning: These might cease to work if package perl is removed.

* print_dependents_warning: Force removal of this package with --force-depends.
* print_dependents_warning: Force removal of this package and its dependents
* print_dependents_warning: with --force-removal-of-dependent-packages.

root@localhost:~# opkg remove qt4-embedded
No packages removed.
Collected errors:
* print_dependents_warning: Package qt4-embedded is depended upon by packages:
* print_dependents_warning:     task-qt4e-base
* print_dependents_warning: These might cease to work if package qt4-embedded is removed.

* print_dependents_warning: Force removal of this package with --force-depends.
* print_dependents_warning: Force removal of this package and its dependents
* print_dependents_warning: with --force-removal-of-dependent-packages.
root@localhost:~# opkg remove task-qt4e-base
No packages removed.
Collected errors:
* print_dependents_warning: Package task-qt4e-base is depended upon by packages:
* print_dependents_warning:     chumby-qt-remote
* print_dependents_warning:     chumby-netvserver
* print_dependents_warning:     chumby-qt-reset
* print_dependents_warning:     chumby-netvbrowser
* print_dependents_warning: These might cease to work if package task-qt4e-base is removed.

* print_dependents_warning: Force removal of this package with --force-depends.
* print_dependents_warning: Force removal of this package and its dependents
* print_dependents_warning: with --force-removal-of-dependent-packages.
------------------------------------------------------------------

Re: opkg update failure

we haven't fully debugged the gcc-only toolchain yet, so you're definitely in deep water. If you end up in trouble, here's a link to an image that you can use to restore:

http://buildbot.chumby.com.sg/build/sil … etv.img.gz

You can download this and do a

zcat rom-chumby-silvermoon-netv-chumby-flash-image-netv.img.gz | dd of=/dev/sdX bs=8M

Assuming you have a linux box and you can mount the SD card as a /dev/sdX device through a USB card reader.

One thing you could do is to use our "testing" image, it has a bigger root partition on it to accommodate a full python build.

http://buildbot.chumby.com.sg/build/sil … ing.img.gz

Follow the above instructions to dd it to your card, and it should create your device but with / having a larger size that should ease the installation of gcc.

One thing that is on our list to do is to remove all of the excess cruft built into the system like qt examples and so forth, and also pare down the gcc build tree so that it installs more easily, but we haven't gotten to that and most likely won't for a couple of months, we've got a lot of work to do on the UI before we get to features like this. However, the AMI cloud-based build solution is live today and that could resolve your concerns, I'd encourage you to check that out if you can.

7BAA 2E53 01C1 DCFF 497B  E7F0 9699 A303 78F0 D9B9

6 (edited by drazvan 2011-09-30 11:21:47)

Re: opkg update failure

Hi Bunnie,

I was able to work around the limited space in the root partition by doing the following. Please note that while I have tested this, it has only been on my NeTV (one device). I can't see how you could break anything with it (since root is never mounted read write in this scenario), but be careful.

---------

mkdir /tmp/roroot
mount / /tmp/roroot -o bind
mkdir /tmp/unionroot
mkdir /media/storage/newroot
mount -w -t unionfs -o dirs=/media/storage/newroot=rw:/tmp/roroot=ro unionfs /tmp/unionroot
mount /var/volatile /tmp/unionroot/var/volatile -o bind
chroot /tmp/unionroot /bin/bash
mount -a
mount devpts /dev/pts -t devpts
mount tmpfs /dev/shm -t tmpfs -o rw,mode=777

opkg install task-sdk-native
opkg install libgcc-dev

-------------------------------------

The last opkg install (for libgcc-dev) was required to make the linker work (I have no idea why the initial opkg install didn't list it as a requirement).

I am now able to compile stuff directly on the NeTV. The only thing that is required is to run the commands above (minus the opkg installs) every time I log in, to attach the /media/storage part to the rootfs (since it contains gcc and everything else).

Feel free to put this on the Wiki if you want (or I can put it there but I'd rather wait until someone confirms that it works for them too).

Razvan

Re: opkg update failure

I just tested this on v12 firmware. Couple of things are missing from the script:

mount -o remount,rw      at the very top

mkdir /dev/pts              right before the last two mount calls
mkdir /dev/shm

opkg update           right before the opkg install calls

Other than that, seems to work great. Thanks for contributing this, I'll add this to the wiki.

Total usage is 401560 - 116543 = 390017k for the toolchain.

7BAA 2E53 01C1 DCFF 497B  E7F0 9699 A303 78F0 D9B9

Re: opkg update failure

Bunnie, there should be no need to remount root as read write on top, that's exactly what I've been trying to avoid. The unionfs mounts that part readonly and only /media/storage is mounted read-write, so there should be no need to write to the original root at all. I'm not near my NeTV right now to test this, so please let me know if I missed anything.

Best,
Razvan

Re: opkg update failure

err you're right, I added there out of reflex without thinking about it.

7BAA 2E53 01C1 DCFF 497B  E7F0 9699 A303 78F0 D9B9

Re: opkg update failure

The next update will allow you to remove task-qt4e-base, which should free up a large amount of space.  I know on our end, the compressed image got cut almost in half from 110 MB to about 60 MB without that package and its associated dependencies installed.  It's being replaced by a task-qt4e-minimal that just includes the libraries, no examples or demo programs.