public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Attn: gcc maintainer - calm: WARNING: package 'libgccjit0' doesn't have a curr version
Date: Mon, 2 Aug 2021 20:20:50 +0100	[thread overview]
Message-ID: <5124445d-41c0-d0df-29f3-67489b42f489@dronecode.org.uk> (raw)
In-Reply-To: <878s1jvhhb.fsf@Rainer.invalid>

On 02/08/2021 19:17, Achim Gratz wrote:
> Brian Inglis writes:
>> On 2021-08-02 11:20, cygwin-apps-rDBXBDvO6BXQT0dZR+AlfA-XMD5yJDbdMReXY1tMh2IBg@public.gmane.org wrote:
>>> WARNING: package 'libgccjit0' doesn't have a curr version
>>> WARNING: package 'libgccjit0' doesn't have a curr version
>>> WARNING: package 'libgccjit0' doesn't have a curr version
>>> WARNING: package 'libgccjit0' doesn't have a curr version
>>
>> These messages are probably appearing on all package upload reports.
> 
> So what, it's just a warning?  This package is indeed not yet available
> as "current" because it's a new package introduced as "test".

Yeah.

Unfortunately, because of the way calm works, this warning appears in 
the report for any upload, which is perhaps confusing.

I've configured a suppression for this warning (which is what I usually 
do when this situation is intended).

  reply	other threads:[~2021-08-02 19:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <162792485893.1067698.6637349784371762085@server2.sourceware.org>
2021-08-02 17:30 ` Brian Inglis
2021-08-02 18:17   ` Achim Gratz
2021-08-02 19:20     ` Jon Turney [this message]
2021-08-02 20:52       ` 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=5124445d-41c0-d0df-29f3-67489b42f489@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --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).