public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Libor Ukropec <ace@seznam.cz>, Jari Aalto <jari.aalto@cante.net>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ATTN MAINTAINER] tig
Date: Mon, 16 Jan 2023 12:42:31 +0000	[thread overview]
Message-ID: <9fb74d49-b550-5b7e-0fac-36486495d1a4@dronecode.org.uk> (raw)
In-Reply-To: <df141358-473d-8b3d-e264-093ea6b65eb8@seznam.cz>

On 13/01/2023 16:59, Libor Ukropec via Cygwin-apps wrote:
> Dne 10.01.2023 v 15:04 Jari Aalto via Cygwin-apps napsal(a):
> 
>>
>> Hi, Thanks for the heads up. I've uploaded new version and added the
>> *.cygport in my Github repository of tig for possible new maintainer
>> in the future.
>>
>> The patches deal some fixes in the xmlto(1) of manual pages build.
>>
>> Jari
>>
> Hi Jari,
> 
> I updated to the latest tig, but when executing, it complains about 
> missing dependency, but recently I saw many updates to the cygwin 
> packages. Any idea if other package was broken, or tig is missing some 
> dependency in the metadata?
> 
> C:/cygwin64/bin/tig.exe: error while loading shared libraries: 
> cygpcreposix-0.dll: cannot open shared object file: No such file or 
> directory
> 
> Manual installation of "libpcreposix0 8.45-1" seems resolving the problem.

Libor,


Thanks for reporting this.

I added libpcre1 and libpcreposix0 to the requires: for tig.

Jari,

Please update your local copy, to try to ensure these are correct in any 
future release.


  parent reply	other threads:[~2023-01-16 12:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-11 22:15 Libor Ukropec
2022-12-12 16:32 ` Adam Dinwoodie
2022-12-13 17:14   ` Libor Ukropec
2022-12-13 18:32     ` Adam Dinwoodie
2022-12-13 22:05       ` Libor Ukropec
2023-01-10 14:04     ` Jari Aalto
2023-01-13 16:59       ` Libor Ukropec
2023-01-13 17:06         ` Libor Ukropec
2023-01-13 19:23           ` Brian Inglis
2023-01-13 19:40           ` Adam Dinwoodie
2023-01-16 12:42         ` Jon Turney [this message]
2023-01-25 11:41           ` Jari Aalto

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=9fb74d49-b550-5b7e-0fac-36486495d1a4@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=ace@seznam.cz \
    --cc=cygwin-apps@cygwin.com \
    --cc=jari.aalto@cante.net \
    /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).