opkg issues. best way to run opkg

[Tick Chen]

Hi, 
  Yes, opkg will try to download the signature file to see if the
repository is signed. It will not hurt operations but showing warning
that the repository is not signed. 
  This feature is left for the future. 

Cheers, 
Tick 

On Wed, Jul 16, 2008 at 12:07:40PM +0200, Cédric Berger wrote:
> Hi,
> I tried an opkg upgrade yesterday and I had exactly the same
> question... (I have no answer though)
> 
> About "Failed to download  xxx.sig" and "Signature check failed", it
> think it was mentioned in the mailing list that it is just because
> signatures are not in the repository, but it doesn't hurt the
> operation...
> 
> 
> 
> On Wed, Jul 16, 2008 at 04:20, Yohann (YC) Coppel <leppoc at gmail.com> wrote:
> [...]
> >  * Failed to download
> > http://buildhost.openmoko.org/daily-feed/om-gta02/Packages.sig, error
> > 404
> >
> > as well as "Signature check failed" for anything that is downloaded before.
> 
> [...]
> 
> > The problem is that if I run the command by ssh, the connection is cut
> > during the process:
> > Restarting Dropbear SSH server: Connection to 192.168.0.202 closed by
> > remote host.
> > .... and the upgrade is probably stopped as well.
> >
> > And if I run it from the terminal on the FR, the upgrade is stopped
> > when X restarts at some point during the process.
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.openmoko.org/pipermail/devel/attachments/20080716/93ba58f3/attachment.pgp