All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] rpm: add support for remote package feeds via PACKAGE_FEED_URIS variable
Date: Wed, 15 Mar 2017 13:19:14 +0200	[thread overview]
Message-ID: <9ca28013-06c6-c668-2e42-1d13a75d4331@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LY4pN1n2s9Qe1FSesSRFUcWFLdsQQ6Z2J8-DZqGeBK14Q@mail.gmail.com>

On 03/15/2017 01:13 PM, Burton, Ross wrote:
>
>     +        cls.repo_server.port = 8080
>
>
> What if parallel selftests are running at once?  Can this service be
> started before the image is created, so the right port can be written
> into the image?

I don't know. I only followed what Humberto wrote in the original patch; 
we need to ask him. I'm also not entirely certain that hardcoding the ip 
address will always work, and did not get an answer to that.

Another, more hackish option is to monkey patch the ephemeral port 
before running dnf into the repo config on the image.

Alex



  reply	other threads:[~2017-03-15 11:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 17:27 [PATCH 1/3] rpm: add support for remote package feeds via PACKAGE_FEED_URIS variable Alexander Kanavin
2017-03-14 17:27 ` [PATCH 2/3] lib/oe/package_manager: import rpm signing key to rpmdb Alexander Kanavin
2017-03-14 17:27 ` [PATCH 3/3] selftest/signing.py: verify that images can be created from signed packages Alexander Kanavin
2017-03-15 11:13 ` [PATCH 1/3] rpm: add support for remote package feeds via PACKAGE_FEED_URIS variable Burton, Ross
2017-03-15 11:19   ` Alexander Kanavin [this message]
2017-03-15 12:44     ` Patrick Ohly
2017-03-15 15:38     ` Ibarra Lopez, Humberto
2017-03-15 16:08       ` Richard Purdie
2017-03-15 17:10         ` Ibarra Lopez, Humberto

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=9ca28013-06c6-c668-2e42-1d13a75d4331@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.