From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2015.12.0 released
Date: Tue, 12 Jan 2016 17:31:07 +0100 [thread overview]
Message-ID: <20160112163107.GC18044@pengutronix.de> (raw)
In-Reply-To: <5956ea45a4ca85ba2b41df84468f6cbf@localhost>
Hi,
On Mon, Dec 21, 2015 at 07:09:08PM +0100, Alexander Dahl wrote:
> Am 2015-12-18 12:20, schrieb Michael Olbrich:
> > opkg: version bump 0.2.2 -> 0.3.0
>
> Tested ptxdist 2015.12.0 today and ran into problems with opkg. Firts
> noticed this on executing opkg on the target:
>
> $ opkg update
> Downloading
> http://ada/ipkg-repository/***/dists/***-v2015.11.0-00173-g29ec7212f51b-dirty/Packages.
> Downloading
> http://ada/ipkg-repository/***/dists/***-Lite-v2015.11.0-00173-g29ec7212f51b-dirty/Packages.sig.
> wget: server returned error: HTTP/1.1 404 Not Found
> Collected errors:
> * opkg_download_backend: Failed to download
> http://ada/ipkg-repository/***/dists/***-v2015.11.0-00173-g29ec7212f51b-dirty/Packages.sig,
> wget returned 1.
> * pkg_src_download_signature: Failed to download signature for ptxdist.
>
> Then I went to ptxdist menuconfig and checked my opkg options which were
> just migrated from v2015.10.0:
>
> % grep -i opkg configs/ptxconfig
> PTXCONF_HOST_PACKAGE_MANAGEMENT_OPKG=y
> PTXCONF_HOST_PACKAGE_MANAGEMENT="opkg"
> PTXCONF_HOST_OPKG_UTILS=y
> PTXCONF_HOST_OPKG=y
> PTXCONF_OPKG=y
> # PTXCONF_OPKG_CURL is not set
> # PTXCONF_OPKG_SHA256 is not set
> # PTXCONF_OPKG_OPENSSL is not set
> # PTXCONF_OPKG_SSL_CURL is not set
> PTXCONF_OPKG_OPKG_CONF=y
> PTXCONF_OPKG_OPKG_CONF_HOST="ada"
> PTXCONF_OPKG_OPKG_CONF_URL="src ptxdist
> http://${PTXCONF_OPKG_OPKG_CONF_HOST}/ipkg-repository/${PTXCONF_PROJECT}/dists/${PTXCONF_PROJECT}${PTXCONF_PROJECT_VERSION}"
>
> This is what still worked with ptxdist 2015.10.0 and now does not
> anymore. I checked the prepare stage:
>
> ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
> --libdir=/usr/lib --host=arm-v5te-linux-gnueabi
> --build=x86_64-host-linux-gnu --enable-largefile --disable-static
> --disable-libopkg-api --disable-pathfinder --disable-curl
> --disable-sha256 --disable-openssl --disable-ssl-curl --disable-gpg
>
> Then I poked around in the opkg source and it seems like verify is
> mandatory and the only allowed options are gpg, gpg-asc, and openssl. My
> /etc/opkg/opkg.conf is the one prepared by ptxdist:
>
> option check_signature 0
> #option signature_ca_path /etc/ssl/certs
> #option signature_ca_file /etc/ssl/certs/opkg.crt
>
> The check_signature 0 option does not work. Neither do these:
>
> option signature_type none
> option check_pkg_signature 0
Can you remove the line? I cannot test this right now, but from reading the
code, it looks like nothing means 'false' and 'option signature_type' (with any
argument) mean 'true'.
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:[~2016-01-12 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 11:20 Michael Olbrich
2015-12-21 18:09 ` Alexander Dahl
2015-12-22 11:42 ` [ptxdist] setting up opkg with ptxdist 2015.12.0 (Was: [ANNOUNCE] PTXdist 2015.12.0 released) Alexander Dahl
2016-01-11 12:10 ` [ptxdist] setting up opkg with ptxdist 2015.12.0 Alexander Dahl
2016-01-12 13:47 ` Tim Sander
2016-01-12 16:21 ` Michael Olbrich
2016-01-12 16:44 ` [ptxdist] setting up opkg with ptxdist 2015.12.0 (Was: [ANNOUNCE] PTXdist 2015.12.0 released) Michael Olbrich
2016-01-12 16:31 ` Michael Olbrich [this message]
2016-08-02 8:44 ` [ptxdist] [ANNOUNCE] PTXdist 2015.12.0 released Alexander Dahl
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=20160112163107.GC18044@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