On Sun, May 26, 2013 at 18:23:22 -0700 , Karen Etheridge wrote:
> On Sun, May 26, 2013 at 06:19:35PM -0700, Karen Etheridge wrote:
> > On May 22, I released 1.008009 on top of the last release seen in git.
> > The upload returned HTTP 200, and I also received an indexing
> > acknowledgement in git.
On Mon, May 27, 2013 at 1:05 PM, Karen Etheridge wrote:
> I cannot think of any scenario where I would want to block a duplicate
> upload from the same user but allow a duplicate upload from another user...
> this sounds like a failure in application of the "be liberal in what you
> accept" rule.
On Sun, May 26, 2013 at 10:36:30PM -0400, David Golden wrote:
> There is a restriction on the *tarball* path -- but you uploaded to
> different author directories so that doesn't matter. Basically, you
> just swapped one author for the other as far as PAUSE is concerned.
I cannot think of any sc
On Sun, May 26, 2013 at 9:19 PM, Karen Etheridge wrote:
> - PAUSE should not have indexed the second upload, as there was a version
> conflict
PAUSE only insists that version be non-decreasing. There is no
problem with them being the same. Many distributions manage module
versions by keeping v
[[ This message was both posted and mailed: see
the "To," "Cc," and "Newsgroups" headers for details. ]]
In article <20130527012322.ga72...@tequila.etheridge.ca>, Karen
Etheridge wrote:
> On Sun, May 26, 2013 at 06:19:35PM -0700, Karen Etheridge wrote:
> > On May 22, I released 1.008009 on to
On Sun, May 26, 2013 at 06:19:35PM -0700, Karen Etheridge wrote:
> On May 22, I released 1.008009 on top of the last release seen in git.
> The upload returned HTTP 200, and I also received an indexing
> acknowledgement in git.
The filename we both uploaded was local-lib-1.008009.tar.gz.
Below is
In February, apeiron released local-lib-1.008009, but forgot to update the
remote git repository (oops!) He received an email acknowledgement from
PAUSE indicating that indexing was successful.
On May 22, I released 1.008009 on top of the last release seen in git.
The upload returned HTTP 200,