Talk:MwExtUpgrader/Flow

I think I saw something about the latest version 0.2 requiring php 8.1. Is this correct? or can I use the latest version with php 8.0?

This tool requires PHP 7.1.3 or higher, include 8.0 and 8.1

Resolved in d2fd566

Great tool, thanks. I'm exactly your target audience, one of the many people update extensions one by one, such as by using ExtensionDistributor, without using git.

When I update my extensions one by one, I currently use wget from the command line in Linux and I end up with a .tar.gz file on my filesystem, which I extract. The timestamps on the .tar.gz file and all the corresponding extracted extension files match the 'commit' timestamp for the extension. This is useful to me to provide an audit trail of the updated extension back to the source repository.

In my testing of this tool I'm noticing that the timestamps in the extensions directory all match when the tool was run, not the source repository dates, so I don't have the same audit trail.

Could this tool be changed so the updated extensions (and skins BTW) have timestamps that match the source respository. The curl '--remote-time' option might be helpful.

What you mean is to ensure that the modification time of the extension file upgraded through mwExtUpgrader is the same as the modification time manually upgraded through wget & tar?

I've done some further testing today and the timestamps on the tar.gz files that come from Special:ExtensionDistributor are the timestamp at the time of the download.

However, when the tar file is extracted, the timestamps on the extracted files. For example, for downloading the Cite extension for 1.35, the tarball reveals:

tar -t -v --full-time -f Cite-REL1_35-52f3cf3.tar.gz
drwxr-xr-x extdist/extdist   0 2020-12-31 20:03:18 Cite/
drwxr-xr-x extdist/extdist   0 2020-12-31 20:03:18 Cite/src/
-rw-r--r-- extdist/extdist 2988 2020-12-31 20:03:18 Cite/src/FootnoteMarkFormatter.php
-rw-r--r-- extdist/extdist 3413 2020-12-31 20:03:18 Cite/src/ErrorReporter.php
-rw-r--r-- extdist/extdist 9498 2020-12-31 20:03:18 Cite/src/ReferencesFormatter.php
.
.
.

My "improvement" request is to have this tool leave the updated extension files to match the timestamps contained within the equivalent tar download.

Hopefully that further explains or clarifies what I'm asking about.

I file a github issue to track you idea.

The new version has been released. The version can be resolve you needs.

Tested the new version and appreciate the change. Very helpful. Thank you.

Do I simply download this into the Extensions Folder and then call the script within the Extensions Folder? Thanks!

MwExtUpgrader can be placed in any location. It does not depend on the current working directory.

Just figured it out but thanks for the answer. For others like me here is what I did: I put the code into the Extensions folder and it requested my absolute path. Then it was cool as it asked what version I wanted to go to and it did include MW 1.35. It did tell me: ExtensionDistributor unsupported Maps, ExtensionDistributor unsupported Purge, ExtensionDistributor unsupported EmbedVideo, ExtensionDistributor unsupported Validator.

It also said: "In UpgradeTask.php line 163:

 file_get_contents(/home/iafstghq/digitalmatrixgroup.com/extensions/Wikibase/extension.json): failed to open stream: No such file or directory"

I presume this is something I have to go find as I am upgrading and have errors anyway.

Got it all resolved. It dealt with I copied the old composer.json over. Great script my friend!!!!

Thanks report. This is a bug that not check if extension.json exists before reading it.

Thanks report. This is a bug that not check if extension.json exists before reading it.

"Many people are updated one by one via ExtensionDistributor, without git. " come on - does anybody ever check what is written?

Not everyone is a native English speaker. Improving it yourself would be nicer and more useful than just complaining.

@Clump I tried to use it with no luck,

Could not open input file: mwExtUpgrader.phar

i managed to run,

with a warning message: Note that this release of code is not stable. Do not use for production.

shall I proceed with it?

It is in beta, so that's a standard kind of notice. I know nothing about this code though. @星耀晨曦 is the author and may be able to offer better advice/help, or you can ask on their github issues page.

For the stability of your wiki and this project has not been widely used, there may be bugs that affect the stability. So before run, the script will prompt you.