[Wikitech-l] The difference between fileexists-no-change and backend-fail-alreadyexists for action=upload

Hi there, Hope I've found the correct list for asking this question. I was setting up a CI test case for my MediaWiki Client Library to run a bot that will upload a file to https://en.wikipedia.beta.wmflabs.org in chunked stash mode. For most of the time, when I perform the final upload with

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

On Fri, Nov 15, 2019 at 7:19 PM Sam Wilson wrote: > Where does the mediawiki/mediawiki package come from? It's no longer on > Packagist; how does Composer know where to get it? It should certainly > not appear as a requirement for any package. > ComposerHookHandler adds it programmatically. As

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

Where does the mediawiki/mediawiki package come from? It's no longer on Packagist; how does Composer know where to get it? It should certainly not appear as a requirement for any package. As for removing the functionality: do you mean the functionality of the Composer merge plugin? i.e. that

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

On Fri, Nov 15, 2019 at 8:16 AM Brad Jorsch (Anomie) wrote: > It also predated T467 RfC: Extension management with Composer > , which rejected the proposal to > manage extensions via composer. Which raises the question: should this functionality stay in

[Wikitech-l] WM Technical Conference 2019 update - day 4

Hello and thanks for reading! We wanted to give a quick update on what happened during the final day of the Wikimedia Technical Conference , in Atlanta, Georgia. *Friday

Re: [Wikitech-l] help once

Hi, I didn't quite understand this mail. Can you clarify? Best regards, Zoran. pet, 15. nov 2019. 20:16 Fokou Joel je napisao/la: > I am a student in the Faculty of Engineering and Technology in > University of Buea(Cameroon). > Thank you! > > ___ >

[Wikitech-l] help once

I am a student in the Faculty of Engineering and Technology in University of Buea(Cameroon). Thank you! ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

On Fri, Nov 15, 2019 at 11:06 AM Lucas Werkmeister < lucas.werkmeis...@wikimedia.de> wrote: > That was six years ago, predating extension registration – I would assume > that nowadays extensions are supposed to declare their compatible MediaWiki > versions in extension.json > < >

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

That was six years ago, predating extension registration – I would assume that nowadays extensions are supposed to declare their compatible MediaWiki versions in extension.json (details

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

See https://github.com/wikimedia/mediawiki/commit/3307d4957925df319df2b84cfc3e6f1680d0632a "This change allows extensions to specify they depend on a specific version or version range of MediaWiki. This is done by adding the package mediawiki/mediawiki in their composer.json require section."

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

To enable extensions to declare a version constraint on MW, so an incompatible version of an extension is not installed in the first place instead of crashing MW later on. Stephan ‐‐‐ Original Message ‐‐‐ On Friday, November 15, 2019 4:27 PM, Florian Schmidt wrote: > Extensions can

Re: [Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

as far as I know, extensions shouldn't be declaring a dependency on MediaWiki in composer.json and if one is, it should probably be fixed. On Fri, Nov 15, 2019 at 9:50 AM Stephan Gambke via Wikitech-l < wikitech-l@lists.wikimedia.org> wrote: > > When running `composer update` MediaWiki injects a

[Wikitech-l] Composer does not know mediawiki/mediawiki on dry-runs

When running `composer update` MediaWiki injects a mediawiki/mediawiki package, so extensions can declare a dependency on a particular MW version range. However, when doing a `composer update --dry-run` this package gets not injected causing the dry run to fail. Does anybody know a