All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Assaf Gordon <assafgordon@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.30-rc2
Date: Tue, 30 May 2017 15:28:43 +0200	[thread overview]
Message-ID: <20170530132843.v4mykfwkrwdkxolt@ws.net.home> (raw)
In-Reply-To: <E6F9AA27-1BC9-4595-9FB2-30F1BA3663CA@gmail.com>

On Tue, May 30, 2017 at 01:03:53AM -0400, Assaf Gordon wrote:
> Hello
> 
> > On May 23, 2017, at 06:50, Karel Zak <kzak@redhat.com> wrote:
> > 
> > The util-linux release v2.30-rc2 is available at
> > 
> >  http://www.kernel.org/pub/linux/utils/util-linux/v2.30/
> 
> Few results from various system:
> 
> 1.
> On several systems which do not have ncurses development files
> installed, the "configure" script does not detect it,
> and completion later fails.
> Example with Debian 8.1:

I see where is the problem. We assume that successful ncurses-config
call means that devel stuff is installed. Unfortunately, on Debian 8
this script is installed by ncurses-bin where is nothing like header
files etc. 

IMHO it's packaging bug, but I'll improve our build system to be more
paranoid...

   Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  parent reply	other threads:[~2017-05-30 13:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 10:50 [ANNOUNCE] util-linux v2.30-rc2 Karel Zak
2017-05-30  5:03 ` Assaf Gordon
2017-05-30  9:27   ` Karel Zak
2017-05-30 13:28   ` Karel Zak [this message]
2017-05-30 15:18   ` Karel Zak
2017-05-31  3:48     ` Assaf Gordon
2017-05-31  9:16       ` Karel Zak
2017-05-31 17:41         ` Assaf Gordon
2017-05-31 18:36           ` Ruediger Meier
2017-05-31 20:05             ` Assaf Gordon
2017-05-31 20:36               ` Ruediger Meier
2017-05-31 20:03           ` Ruediger Meier

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=20170530132843.v4mykfwkrwdkxolt@ws.net.home \
    --to=kzak@redhat.com \
    --cc=assafgordon@gmail.com \
    --cc=util-linux@vger.kernel.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.