From: Martin Jansa <martin.jansa@gmail.com>
To: "André Draszik" <git@andred.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: \n in DESCRIPTION creates invalid (ipk) packages? (was: Re: [oe][meta-networking][PATCH 0/2] ncp - a fast file copy tool for LANs)
Date: Wed, 16 Nov 2016 11:59:27 +0100 [thread overview]
Message-ID: <20161116105927.GB16451@jama> (raw)
In-Reply-To: <1479287229.3131.10.camel@andred.net>
[-- Attachment #1: Type: text/plain, Size: 2026 bytes --]
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
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 169 bytes --]
prev parent reply other threads:[~2016-11-16 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161115154311.30118-1-git@andred.net>
[not found] ` <1479230361.3131.6.camel@andred.net>
2016-11-16 9:07 ` \n in DESCRIPTION creates invalid (ipk) packages? (was: Re: [oe][meta-networking][PATCH 0/2] ncp - a fast file copy tool for LANs) André Draszik
2016-11-16 10:59 ` Martin Jansa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161116105927.GB16451@jama \
--to=martin.jansa@gmail.com \
--cc=git@andred.net \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox