All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yong Li" <yong.b.li@linux.intel.com>
To: "'Alexander Amelkin'" <a.amelkin@yadro.com>, <openbmc@lists.ozlabs.org>
Subject: RE: license conflicts with OpenSSL
Date: Wed, 4 Dec 2019 10:18:27 +0800	[thread overview]
Message-ID: <001201d5aa49$1e12c9e0$5a385da0$@linux.intel.com> (raw)
In-Reply-To: <e90e0947-6024-7967-f62f-43f899ed0764@yadro.com>

Thanks Alexander for your information.

The .bb file in openBMC project also needs to remove the ncurse dependency.

Will monitor the PR and  submit the changes, also enabling " --disable-ipmishell"

Thanks,
Yong

-----Original Message-----
From: Alexander Amelkin <a.amelkin@yadro.com> 
Sent: Monday, December 2, 2019 11:13 PM
To: Yong Li <yong.b.li@linux.intel.com>; openbmc@lists.ozlabs.org
Subject: Re: license conflicts with OpenSSL

02.12.2019 4:08, Yong Li wrote:
> Thanks Alexander for your quick response!
>
> My understanding is that you will perform some changes in the upstream 
> https://github.com/ipmitool/ipmitool, to remove these unused/obsolete 
> dependencies.

You're correct. I've already posted a PR to remove the ncurses dependency:
https://github.com/ipmitool/ipmitool/pull/175

I'd like at least Vernon to approve it before I merge it into master.

> But I notice the ipmitool_1.8.18.bb file in openembedded is using 
> these
> .tar.bz2 files from sourceforge.net. Just want to know do you upload 
> the new versions to sourceforge.net?

No, the sourceforge.net is abandoned and will not be updated.

New releases will be available at https://github.com/ipmitool/ipmitool/releases

I don't yet have any schedule for the next release though.

WBR, Alexander.

      reply	other threads:[~2019-12-04  2:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29  6:56 license conflicts with OpenSSL Yong Li
2019-11-29 11:27 ` Alexander Amelkin
2019-12-02  1:08   ` Yong Li
2019-12-02 15:12     ` Alexander Amelkin
2019-12-04  2:18       ` Yong Li [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='001201d5aa49$1e12c9e0$5a385da0$@linux.intel.com' \
    --to=yong.b.li@linux.intel.com \
    --cc=a.amelkin@yadro.com \
    --cc=openbmc@lists.ozlabs.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 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.