From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <cygwin-apps@cygwin.com>
Subject: pdfgrep package uploads not as I expected
Date: Wed, 19 May 2021 21:47:30 -0400 [thread overview]
Message-ID: <079b01d74d1a$1873a700$495af500$@pdinc.us> (raw)
Looks like I did this wrong.
I wanted to provide:
2.1.3-0.1621294138.9b5c98a - test from pdfgrep HEAD commit
2.1.2-1 - test (for now) of most recent v2 release
1.4.1-2 - test (for now) of the rebuild of the last v1 release.
After one week was going to
ssh cygwin@cygwin.com untest pdfgrep-1.4.1-2
ssh cygwin@cygwin.com untest pdfgrep-2.1.2-1
but the calm report ignored 2.1.2 and "vaulted" 1.4.1 .
Is it not possible to provide more than one test package?
-Jason
> -----Original Message-----
> From: cygwin-apps
> Sent: Wednesday, May 19, 2021 8:51 PM
> Subject: calm: cygwin package upload report for Jason Pyeron
>
> INFO: adding 2 package(s) for arch x86
> INFO: move from Jason Pyeron's upload area to release area:
> INFO: x86/release/pdfgrep/pdfgrep-2.1.3-0.1621294138.9b5c98a-src.hint
> INFO: x86/release/pdfgrep/pdfgrep-2.1.3-0.1621294138.9b5c98a-src.tar.xz
> INFO: x86/release/pdfgrep/pdfgrep-2.1.3-0.1621294138.9b5c98a.hint
> INFO: x86/release/pdfgrep/pdfgrep-2.1.3-0.1621294138.9b5c98a.tar.xz
> INFO: x86/release/pdfgrep/pdfgrep-debuginfo/pdfgrep-debuginfo-2.1.3-
> 0.1621294138.9b5c98a.hint
> INFO: x86/release/pdfgrep/pdfgrep-debuginfo/pdfgrep-debuginfo-2.1.3-
> 0.1621294138.9b5c98a.tar.xz
> INFO: adding 2 package(s) for arch x86_64
> INFO: move from Jason Pyeron's upload area to release area:
> INFO: x86_64/release/pdfgrep/pdfgrep-2.1.3-0.1621294138.9b5c98a-src.hint
> INFO: x86_64/release/pdfgrep/pdfgrep-2.1.3-0.1621294138.9b5c98a-src.tar.xz
> INFO: x86_64/release/pdfgrep/pdfgrep-2.1.3-0.1621294138.9b5c98a.hint
> INFO: x86_64/release/pdfgrep/pdfgrep-2.1.3-0.1621294138.9b5c98a.tar.xz
> INFO: x86_64/release/pdfgrep/pdfgrep-debuginfo/pdfgrep-debuginfo-2.1.3-
> 0.1621294138.9b5c98a.hint
> INFO: x86_64/release/pdfgrep/pdfgrep-debuginfo/pdfgrep-debuginfo-2.1.3-
> 0.1621294138.9b5c98a.tar.xz
> INFO: vaulting 2 old package(s) for arch x86_64
> INFO: move from release area to vault:
> INFO: x86_64/release/pdfgrep/pdfgrep-1.4.1-2-src.hint
> INFO: x86_64/release/pdfgrep/pdfgrep-1.4.1-2-src.tar.xz
> INFO: x86_64/release/pdfgrep/pdfgrep-1.4.1-2.hint
> INFO: x86_64/release/pdfgrep/pdfgrep-1.4.1-2.tar.xz
> INFO: x86_64/release/pdfgrep/pdfgrep-debuginfo/pdfgrep-debuginfo-1.4.1-2.hint
> INFO: x86_64/release/pdfgrep/pdfgrep-debuginfo/pdfgrep-debuginfo-1.4.1-2.tar.xz
> SUMMARY: 24 INFO(s)
next reply other threads:[~2021-05-20 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 1:47 Jason Pyeron [this message]
2021-05-20 14:18 ` Jon Turney
2021-05-20 14:47 ` Jason Pyeron
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='079b01d74d1a$1873a700$495af500$@pdinc.us' \
--to=jpyeron@pdinc.us \
--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).