andk
fast deletion interface
from QAH Berlin 2015: we need an interface to delete distributions from PAUSE that takes effect sooner than in 3 days.
(there are concerns about whether backpan will always have a chance to archive the dist, which should be examined.)
I suggest there may be a desire for a "Also skip backpan" option for very fast deletes where a backup copy is undesirable, for example, cases where private details leak in to a release, this gets it killed before replication happens and without needing to get proper takedowns performed manually.
Without that option, I would desire some sort of priority signal sent to the backpan mirror to make that version backup happen ASAP, with PAUSE checking backpan every hour or so for slated removals to be replicated, and then nuke them when backpan has mirrored it.
On Sat, 09 May 2015 20:21:53 -0700, Kent Fredric [email protected] said:
I suggest there may be a desire for a "Also skip backpan" option for very fast deletes where a backup copy is undesirable, for example, cases where private details leak in to a release, this gets it killed before replication happens and without needing to get proper takedowns performed manually.
Without that option, I would desire some sort of priority signal sent to the backpan mirror to make that version backup happen ASAP, with PAUSE checking backpan every hour or so for slated removals to be replicated, and then nuke them when backpan has mirrored it.
This desire can only be rejected, it is unfulfillable. CPAN infrastructure is faster than you seem to believe. Every file you upload is squirreled away before anybody can click any delete button.
andreas
This desire can only be rejected, it is unfulfillable. CPAN infrastructure is faster than you seem to believe. Every file you upload is squirreled away before anybody can click any delete button.
I don't mean that it will be "flawless", you will still of course need some other kind of ass-cover for everywhere else it replicates to.
Its just a "minimize damage" step. Though I guess if its already hit a primary mirror then you're already screwed I guess.
On a related note, once something is on CPAN, MetaCPAN doesn't have a good way of deleting things. https://github.com/CPAN-API/cpan-api/issues/359
