On Wed, Nov 16, 2016 at 09:07:09AM +0000, André Draszik wrote:
> On Tue, 2016-11-15 at 17:19 +0000, André Draszik wrote:
> > On Tue, 2016-11-15 at 15:43 +0000, André Draszik wrote:
> > > "ncp" is a utility for copying files in a LAN. It has absolutely
> > > no security or integrity checking, no throttling, no features,
> > > except one:
> > >   you don't have to type the coordinates of your peer.
> > 
> > Hm, hold on. Something went wrong along the way. I can't actually install
> > it
> > anymore:
> > 
> > root@poky:~# opkg update
> > Package ncp-dbg version 1.2.4-r0 has no valid architecture, ignoring.
> > Package ncp-dev version 1.2.4-r0 has no valid architecture, ignoring.
> > Package ncp-doc version 1.2.4-r0 has no valid architecture, ignoring.
> > Package ncp version 1.2.4-r0 has no valid architecture, ignoring.
> > 
> > root@poky:~# opkg install ncp
> > Package ncp-dbg version 1.2.4-r0 has no valid architecture, ignoring.
> > Package ncp-dev version 1.2.4-r0 has no valid architecture, ignoring.
> > Package ncp-doc version 1.2.4-r0 has no valid architecture, ignoring.
> > Package ncp version 1.2.4-r0 has no valid architecture, ignoring.
> > Collected errors:
> >  * opkg_prepare_url_for_install: Couldn't find anything to satisfy 'ncp'.
> 
> It looks like this was caused by additional \n in the DESCRIPTION string. Is
> it expected that those cause the packaging process to create apparently
> invalid ipk packages?

Was the \n at the end of DESCRIPTION?
If it leads into empty line in status file, then it's considered
separator for next package, see:
http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/commit/?id=7f0a7976c29b34feaf4f6b00f0a63626614d1c7d

> 
> 
> 
> 
> Cheers,
> Andre'
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> [email protected]
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: [email protected]

Attachment: signature.asc
Description: Digital signature

-- 
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to