Re: Help with PAUSE mechanics - replacing a bad module

Replies are listed 'Best First'.
Re^2: Help with PAUSE mechanics - replacing a bad module by PUCKERING (Sexton) on Aug 31, 2022 at 04:06 UTC
I saw the reset feature — which comes with a caution against using it. But there doesn’t seem to be any explanation as to how it works. The version number is a component of the tarball name. Is the tarball renamed? And the version number is embedded within the module source files inside the tarball . Are those changed? I presume not. I’m sure all these questions will be answered once I stumble through this process the first time. But it would be nice to know in advance. The documentation is pretty thin on PAUSE mechanics. Perhaps resetting the version will simply lower the current module down the list where it effectively becomes irrelevant. If I then republish it with a new, higher version number, PAUSE will see it as a newer version. I still have a window of opportunity to cancel the deletions I submitted. Tomorrow, I’ll try cancelling the deletions try resetting the version number. I just hope that doesn’t take a week.	[reply]
Re^3: Help with PAUSE mechanics - replacing a bad module by SankoR (Prior) on Aug 31, 2022 at 15:33 UTC
> I saw the reset feature — which comes with a caution against using it. The main caveat is that anyone who might have installed your dist with the unwanted version number won't automatically downgrade to a more recently uploaded version. All cpan clients will allow for manually downgrading versions but none that I know of do it based on upload date. > But there doesn’t seem to be any explanation as to how it works. The version number is a component of the tarball name. It doesn't necessarily need to be for the process to work. The PAUSE indexer parses the files in your upload to gather package-level version numbers. You could upload your dist as `Some_Project.late_Aug.tar.gz` or even `da39a3ee5e6b4b0d3255bfef95601890afd80709.tar.gz`; PAUSE is unconcerned with the name of the tarball as long as it is unique. > Is the tarball renamed? And the version number is embedded within the module source files inside the tarball . Are those changed? I presume not. No, nothing inside the tar is ever modified by PAUSE (anymore; there was an old bug where Windows generated tarballs with world writable files about 10 years ago and the system would go in and fix that and produce a second, renamed dist but I don't think it does that anymore). The version info stored in PAUSE is simply cleared from the backend. It'll be a blank spot in the database which allows you to downgrade version numbers whenever that package is indexed again (manually or on next upload). Resetting the version is instantaneous.	[reply] [d/l] [select]
Re^2: Help with PAUSE mechanics - replacing a bad module by PUCKERING (Sexton) on Aug 31, 2022 at 04:18 UTC
Just saw your update about re-indexing. Ok, the picture is becoming clearer. Thanks for the info and suggestions.	[reply]


Perl: the Markov chain saw
	PerlMonks