From: Jon Turney <jon.turney@dronecode.org.uk>
To: Marco Atzeri <marco.atzeri@gmail.com>
Cc: cygwin-apps@cygwin.com
Subject: Re: [scallywag] libksba-1.6.5-1 install anomaly
Date: Tue, 19 Dec 2023 11:24:18 +0000 [thread overview]
Message-ID: <72c0b612-71fa-4c12-a604-a2f004c29e94@dronecode.org.uk> (raw)
In-Reply-To: <e2e0eb82-a9b1-4f32-a2d1-7ede57507b41@gmail.com>
On 19/12/2023 05:29, Marco Atzeri via Cygwin-apps wrote:
> Hi Jon
>
> on jobs 7426 and (rerun) 7428 I see that a file is built
> but not installed
>
> ------------------------------------------
> config.status: creating src/ksba-config
> ...
> >>> libksba-devel-1.6.5-1.tar.xz
> tar: usr/bin/ksba-config: Cannot stat: No such file or directory
> ------------------------------------------
>
> but if I run exacly the same jobs locally, the file is installed and
> packed as expected
This is weird. But this seems to be by upstream design:
Changelog
> 2022-03-31 NIIBE Yutaka <gniibe@fsij.org>
>
> build: When no gpg-error-config, not install ksba-config.
> + commit 41000330cdba87afdf9ea0b481e0260dab262a54
> * configure.ac (USE_GPGRT_CONFIG): New.
> * src/Makefile.am [USE_GPGRT_CONFIG]: Conditionalize the install
> of ksba-config.
>
[...]
>
> Any clue if I should add something to the
>
> BUILD_REQUIRES="libgpg-error-devel pkg-config"
It seems the latest libgpg-error-devel doesn't provide gpg-error-config.
And indeed, upgrading to your recent update to libgpg-error-devel allows
reproducing the problem locally.
next prev parent reply other threads:[~2023-12-19 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 5:29 Marco Atzeri
2023-12-19 11:24 ` Jon Turney [this message]
2023-12-19 18:15 ` Marco Atzeri
2023-12-19 16:01 ` [Attn. MAINTAINER] gpg2 ASSI
2023-12-19 18:12 ` Marco Atzeri
2023-12-19 21:38 ` [scallywag] libksba-1.6.5-1 install anomaly Brian Inglis
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=72c0b612-71fa-4c12-a604-a2f004c29e94@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=marco.atzeri@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).