public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.11.2-0.1
Date: Tue, 30 Oct 2018 12:46:00 -0000	[thread overview]
Message-ID: <f19c1b42-4366-6caa-457a-886eab8d39f8@gmail.com> (raw)
In-Reply-To: <20181030114509.GZ3310@calimero.vinschen.de>

Am 30.10.2018 um 12:45 schrieb Corinna Vinschen:
> On Oct 30 12:41, Marco Atzeri wrote:
>> Am 30.10.2018 um 10:12 schrieb Corinna Vinschen:
>>> Hi folks,
>>>
>>>
>>> I uploaded a new Cygwin test release 2.11.2-0.1
>>>
>>
>> the files are up, but the setup.ini does not show them
>> problem with any ovverride.hint ?
>
> I marked them as test release via cygport.  There's no override.hint but
> the test marker in the versioned hint file.  No idea what else to do.
>

It seems the "cygwin" portion of setup.ini was not updated at all.
It is reporting the 2.10.0-1 but the files are not anymore there.

I guess we need to wait the 4 hours round to fully update the setup.ini.
I tested locally with calm the "test:" tag on specific hint files and it
works fine

Regards
Marco


---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2018-10-30 12:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30  9:24 Corinna Vinschen
2018-10-30 11:41 ` Marco Atzeri
2018-10-30 11:45   ` Corinna Vinschen
2018-10-30 12:46     ` Marco Atzeri [this message]
2018-10-30 14:25       ` Achim Gratz
2018-10-31 13:54 Niels Kristian "Ænkå" Jensen
2018-10-31 15:16 ` Marco Atzeri
2018-11-01  8:20   ` Niels Kristian "Ænkå" Jensen
2018-11-01 10:13     ` Marco Atzeri

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=f19c1b42-4366-6caa-457a-886eab8d39f8@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@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).