From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] rootfs: package
Date: Tue, 4 Dec 2018 14:39:33 +0100 [thread overview]
Message-ID: <20181204133933.tee2q3eamkq7tdjk@pengutronix.de> (raw)
In-Reply-To: <CAA0ZWqbTSd9kMKCoX7zM_8xXZmG-NLBzqUA3BX8jg=UsvP2HFw@mail.gmail.com>
On Tue, Dec 04, 2018 at 02:25:15PM +0100, Andreas Friesen wrote:
> Also I extracted my opkg.conf from ptxdist after little hack in
> /usr/local/lib/ptxdist-2018.11.0/scripts/lib/ptxd_make_image_prepare_work_dir.sh
>
> ptxd_make_image_extract_xpkg_files() {
> ...
> cat "${xpkg_conf}" > /tmp/opkg.conf &&
> ..
> }
>
>
> ââ[$] <> cat opkg.conf
> option force_postinstall 1
> #
> # /etc/opkg/opkg.conf
> #
> src/gz willi http://willi.devel.hbm.com/clipx/soc-packages
> dest root /
> arch armhf 10
> arch all 1
> arch noarch 1
> option check_signature 0
> #option signature_ca_path /etc/ssl/certs
> #option signature_ca_file /etc/ssl/certs/opkg.crt
This is generated from projectroot/etc/opkg/opkg.conf. I expect you have
one in your BSP. You need to add the lock_file option there.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-12-04 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 7:35 Andreas Friesen
2018-12-03 22:38 ` Andreas Friesen
2018-12-04 7:50 ` Michael Olbrich
2018-12-04 9:40 ` Andreas Friesen
2018-12-04 10:40 ` Michael Olbrich
2018-12-04 11:47 ` Andreas Friesen
2018-12-04 11:53 ` Andreas Friesen
2018-12-04 11:58 ` Michael Olbrich
2018-12-04 12:47 ` Andreas Friesen
2018-12-04 12:58 ` Michael Olbrich
2018-12-04 13:25 ` Andreas Friesen
2018-12-04 13:39 ` Michael Olbrich [this message]
2018-12-05 6:32 ` Andreas Friesen
2018-12-04 7:49 ` Michael Olbrich
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=20181204133933.tee2q3eamkq7tdjk@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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