From: Yasuhiro KIMURA <yasu@utahime.org>
To: cygwin-apps@cygwin.com
Subject: Re: Update of packages by non-maintainer
Date: Fri, 29 May 2020 07:34:35 +0900 (JST) [thread overview]
Message-ID: <20200529.073435.1952274186863135803.yasu@utahime.org> (raw)
In-Reply-To: <e777c90f-40f9-2276-1e6c-f8e5ee67678e@gmail.com>
Thank for reply, and sorry for late response
I had some troubles to upgrade anthy port to version 0.4 from Debian.
But I managed to success to build new anthy packages and am now
testing them with my daily use.
From: Marco Atzeri <marco.atzeri@gmail.com>
Subject: Re: Update of packages by non-maintainer
Date: Thu, 21 May 2020 23:11:34 +0200
>> currently we have no solution. There were in the past discussion
>> to overcome such problem but they are not yet implemented.
>
> I was wrong, the mechanism was created
>
> https://cygwin.com/packaging-hint-files.html#override.hint
In my case following line should be put as override.hint. Right?
----------------------------------------------------------------------
curr: 0.4-1
----------------------------------------------------------------------
And is there any way to generate override.hint from .cygport file with
cygport command?
---
Yasuhiro KIMURA
next parent reply other threads:[~2020-05-28 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200521.134708.978300984572490822.yasu@utahime.org>
[not found] ` <e40a75dd-5d73-19cd-2eeb-0625bb29d9f8@gmail.com>
[not found] ` <e777c90f-40f9-2276-1e6c-f8e5ee67678e@gmail.com>
2020-05-28 22:34 ` Yasuhiro KIMURA [this message]
2020-05-29 9:59 ` Achim Gratz
2020-06-03 5:31 ` Yasuhiro KIMURA
2020-06-03 16:20 ` Request for review: anthy 9100h+0.4 (Re: Update of packages by non-maintainer) Yasuhiro KIMURA
2020-06-03 16:41 ` Yaakov Selkowitz
2020-06-04 17:04 ` Request for review: anthy 9100h+0.4 Yasuhiro KIMURA
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=20200529.073435.1952274186863135803.yasu@utahime.org \
--to=yasu@utahime.org \
--cc=cygwin-apps@cygwin.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).