public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: <cygwin-apps@cygwin.com>
Subject: Re: [ITA] libiconv-1.16-1, libiconv2-1.16, libcharset1-1.16-1
Date: Sat, 01 Aug 2020 13:18:43 +0900	[thread overview]
Message-ID: <20200801131841.041C.50F79699@gmail.com> (raw)
In-Reply-To: <8c8332f7-b7fb-b42f-9dbd-ed14f18ba69c@gmail.com>

Date: Fri, 31 Jul 2020 06:22:21 +0200
From: Marco Atzeri via Cygwin-apps <cygwin-apps@cygwin.com>

> On 30.07.2020 21:38, Lemures Lemniscati via Cygwin-apps wrote:
> 
> >
> > By the way, when should I promote libiconv-1.16-2 from test to current?
> 
> when you are confident about it. ;-)
> 
> 
> > But, I don't know how to promote.
> > Should I rebuild and release as libiconv-1.16-3 ?
> 
> No. Just remove the "test:" rows from the hint files and re-upload them
> 
> "calm" does not accept new tar files with the same name, but accept
> replacement for the hint files.
> Usually I upload them with lftp, so I do not know if the cygport way
> have some issues.
> 
> If you have problem, I can modify the hint files directly on
> the repository

Thank you, Marco.

I've tried cygport. And it uploads them.

Now, setup.ini is updated. 



Regards,

Lem

  reply	other threads:[~2020-08-01  4:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11  2:03 Lemures Lemniscati
2020-07-11 17:45 ` Marco Atzeri
2020-07-11 22:01   ` Lemures Lemniscati
2020-07-18  8:29     ` Achim Gratz
2020-07-18 10:34       ` Lemures Lemniscati
2020-07-18 10:45         ` Achim Gratz
2020-07-18 11:18           ` Lemures Lemniscati
2020-07-30 19:38             ` Lemures Lemniscati
2020-07-31  4:22               ` Marco Atzeri
2020-08-01  4:18                 ` Lemures Lemniscati [this message]
2020-07-12 22:16   ` Yaakov Selkowitz

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=20200801131841.041C.50F79699@gmail.com \
    --to=lemures.lemniscati@gmail.com \
    --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).