Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Tobias Jakobi" <tobias.jakobi@compleo-cs.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [Kirkstone] joe editor broken with current ncurses
Date: Wed, 22 Nov 2023 07:46:36 -0800	[thread overview]
Message-ID: <31510.1700667996856303830@lists.openembedded.org> (raw)
In-Reply-To: <5528444bae3c60d3541ea04836b764b900c0f123.camel@rpsys.net>

Yeah, the "causing other problems" bit is also what worries me at the moment. In particular because a lot of other packages depend on ncurses. Usually not on libncurses itself, but on libtinfo. Let me know if I can do further tests. I can't guarantee though how much more time I can spend on this. Our product owner is already asking me why stuff is taking so long :D


  reply	other threads:[~2023-11-22 15:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 10:23 [Kirkstone] joe editor broken with current ncurses tobias.jakobi
2023-11-21 10:39 ` [OE-core] " Alexander Kanavin
     [not found]   ` <31510.1700646535220677658@lists.openembedded.org>
2023-11-22  9:57     ` Private: " Alexander Kanavin
2023-11-22 10:10   ` tobias.jakobi
2023-11-22 10:12     ` [OE-core] " Alexander Kanavin
2023-11-22 10:20       ` tobias.jakobi
2023-11-22 10:43         ` [OE-core] " Alexander Kanavin
2023-11-22 10:58           ` Tobias Jakobi
2023-11-22 11:12             ` [OE-core] " Alexander Kanavin
2023-11-22 15:20               ` Tobias Jakobi
2023-11-22 15:37                 ` [OE-core] " Richard Purdie
2023-11-22 15:46                   ` Tobias Jakobi [this message]
2023-11-22 15:52                     ` Richard Purdie
2023-11-22 16:27                     ` Alexander Kanavin

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=31510.1700667996856303830@lists.openembedded.org \
    --to=tobias.jakobi@compleo-cs.com \
    --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