On packages I have not built myself they work.
I have tried these steps:
md5sum data.tar.gz
result:
6e8d3c655d19f6c55c5657b678011e8e data.tar.gz.
And in the control file:
MD5sum: 6e8d3c655d19f6c55c5657b678011e8e
I have also tried with sha256
sha256sum data.tar.gz
result:
a56d8485eae9cc758bf2ba1d1a20490a79237ff538ebbe561c572073ee3a5485 data.tar.gz
And in control file:
SHA256sum: a56d8485eae9cc758bf2ba1d1a20490a79237ff538ebbe561c572073ee3a5485
the result when I try to install my local package:
sudo opkg-cl -verbosity=4 install mypacktest.opk
result:
Collected errors:
* opkg_install_pkg: Package mypack3 md5sum mismatch. Either the opkg or the package index are corrupt. Try 'opkg update'.
* opkg_install_cmd: Cannot install package mypack3.
Am I calculating the checksum on the wrong file? Thanks for any help!
When signing a package list it is calculated on the Packages file, so I assume it should be on the data file for a package.
Regards
Thanks for the response Paul,
It works fine for me to have checksums in the package list, but I would like to also manually download them and be able to verify them later. I assume there must be a way to do this(?) since OPKG do react to having a checksum in the control file of a package and tries to compare it somehow.
These packages are tried to be installed without any repos linking and an empty package list is shown when run "opkg-cl list-installed".
Worst case otherwise I will just have to save the checksum separately as well.
>
>
> Give that a try and let me know if it works.
>
>
>
> --
>
> Paul Barker
>
>
Thanks for your attention, if you have any ideas for how to do this I'd appreciate it! Maybe I just remember wrong that other packages could compare a checksum from their control file instead of using a package list.
If I might be wrong I will double check it as soon as christmas is over! :D
Regards