public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <cygwin-apps@cygwin.com>
Subject: RE: pdfgrep package uploads not as I expected
Date: Thu, 20 May 2021 10:47:43 -0400	[thread overview]
Message-ID: <029b01d74d87$17958e80$46c0ab80$@pdinc.us> (raw)
In-Reply-To: <030fb770-cfe9-7b73-969a-3efa9e34e972@dronecode.org.uk>

> -----Original Message-----
> From: Jon Turney
> Sent: Thursday, May 20, 2021 10:18 AM
> 
> On 20/05/2021 02:47, Jason Pyeron wrote:
> > 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?
> 
> While it's not documented anywhere, the default policy for test packages
> is to retain 2 versions.
> 
> I have unvaulted 1.4.1-2, and added an override for this package.

Thanks and good to know, and in a week that issue should be moot.

<strike>BTW, was x86 missed or did I not wait long enough?</strike> Its there now.

> 
> Please check https://cygwin.com/packages/summary/pdfgrep-src.html is as
> expected.
> 
> Please also consider updating the packaging git repository linked there.

In progress... there are some "house keeping" items for me to do first.

And thanks to everyone with their patience on my obtusity and pedanticism. It has been a learning exercise.


      reply	other threads:[~2021-05-20 14:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20  1:47 Jason Pyeron
2021-05-20 14:18 ` Jon Turney
2021-05-20 14:47   ` Jason Pyeron [this message]

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='029b01d74d87$17958e80$46c0ab80$@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).