From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Cc: Brian Inglis <Brian.W.Inglis@Gmail.com>
Subject: upload to calm: should curr-2 be vaulted while still in setup.ini?
Date: Sat, 8 Oct 2022 13:59:28 -0600 [thread overview]
Message-ID: <af86939e-9009-768a-9410-8f7d84942f8d@SystematicSw.ab.ca> (raw)
In-Reply-To: <166525660793.1154677.14813540275052888381@server2.sourceware.org>
Hi folks,
After upload, noticed in calm deployment log that release current - 2 is
being vaulted, but it's still showing in setup.ini.
If current - 2 is selected in setup, won't this cause setup to fail, as
as it will no longer be available under release/, nor propagated on
mirrors?
> INFO: adding 1 package(s) for arch x86_64 > INFO: move from Brian Inglis's upload area to release area:> INFO:
deploying x86_64/release/cpuid/cpuid-20221003-1-src.hint> INFO:
deploying x86_64/release/cpuid/cpuid-20221003-1-src.tar.xz> INFO:
deploying x86_64/release/cpuid/cpuid-20221003-1.hint> INFO: deploying
x86_64/release/cpuid/cpuid-20221003-1.tar.xz> INFO: vaulting 1 old
package(s) for arch x86_64> INFO: move from release area to vault:>
INFO: vaulting x86_64/release/cpuid/cpuid-20220812-1-src.hint> INFO:
vaulting x86_64/release/cpuid/cpuid-20220812-1-src.tar.xz> INFO:
vaulting x86_64/release/cpuid/cpuid-20220812-1.hint> INFO: vaulting
x86_64/release/cpuid/cpuid-20220812-1.tar.xz> SUMMARY: 12 INFO(s)
[prev]
version: 20220812-2
install: x86/release/cpuid/cpuid-20220812-2.tar.xz 132096
3eb7f8d86db037c242d7dccbd79b28a4a57771eb08f4e187fd5be124e6b3aff4aa615636e83ed39e6529982869460282b195454914ff6ff573ce2f427b58dcad
source: x86/release/cpuid/cpuid-20220812-2-src.tar.xz 139888
e8e958c2f799fdbed04076878f1a2293066f6004dc3754892354f5484bed172e7ae49d0f0043c0a1a4b5ef52a85b803305de136ec5edd71852a3e5dc02d9ac26
depends2: cygwin, perl_base
build-depends: binutils, coreutils, cygport, gcc-core, gzip, make, perl, tar
--
La perfection est atteinte,
non pas lorsqu'il n'y a plus rien à ajouter,
mais lorsqu'il n'y a plus rien à retirer.
-- Antoine de Saint-Exupéry
next parent reply other threads:[~2022-10-08 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166525660793.1154677.14813540275052888381@server2.sourceware.org>
2022-10-08 19:59 ` Brian Inglis [this message]
2022-10-09 6:58 ` ASSI
2022-10-09 13:45 ` 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=af86939e-9009-768a-9410-8f7d84942f8d@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=Brian.W.Inglis@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).