From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin-apps@cygwin.com
Subject: calm warnings for libgfortran5 & libgnat8
Date: Fri, 12 Apr 2019 14:26:00 -0000 [thread overview]
Message-ID: <er71be5k61ih88707tbri2mmkohm4ava10@4ax.com> (raw)
calm sent me the below after I uploaded screen-4.6.2-3. Do I need to do
anything about the warnings? I'm not sure what they're about. I don't think
I have any packages that depend on libgfortran5 or libgnat8, but maybe I'm
wrong.
Thanks,
Andrew
WARNING: package 'libgfortran5' doesn't have a curr version
WARNING: package 'libgfortran5' doesn't have a curr version
WARNING: package 'libgnat8' doesn't have a curr version
WARNING: package 'libgfortran5' doesn't have a curr version
WARNING: package 'libgfortran5' doesn't have a curr version
WARNING: package 'libgnat8' doesn't have a curr version
INFO: adding 2 package(s) for arch x86_64
INFO: move from Andrew Schulman's upload area to release area:
INFO: x86_64/release/screen/screen-4.6.2-3-src.tar.xz
INFO: x86_64/release/screen/screen-4.6.2-3.hint
INFO: x86_64/release/screen/screen-4.6.2-3.tar.xz
INFO: x86_64/release/screen/screen-debuginfo/screen-debuginfo-4.6.2-3.hint
INFO:
x86_64/release/screen/screen-debuginfo/screen-debuginfo-4.6.2-3.tar.xz
INFO: vaulting 2 old package(s) for arch x86_64
INFO: move from release area to vault:
INFO: x86_64/release/screen/screen-4.6.1-1-src.tar.xz
INFO: x86_64/release/screen/screen-4.6.1-1.hint
INFO: x86_64/release/screen/screen-4.6.1-1.tar.xz
INFO: x86_64/release/screen/screen-debuginfo/screen-debuginfo-4.6.1-1.hint
INFO:
x86_64/release/screen/screen-debuginfo/screen-debuginfo-4.6.1-1.tar.xz
SUMMARY: 14 INFO(s), 6 WARNING(s)
next reply other threads:[~2019-04-12 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 14:26 Andrew Schulman [this message]
2019-04-12 16:10 ` Jon Turney
2019-04-12 16:16 ` Andrew Schulman
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=er71be5k61ih88707tbri2mmkohm4ava10@4ax.com \
--to=schulman.andrew@epa.gov \
--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).