[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-05-18 Thread Stashbot
Stashbot added a comment. Mentioned in SAL (#wikimedia-cloud) [2019-05-18T11:13:41Z] PAWS update helm chart to point to new singleuser image (T217908 ) TASK DETAIL https://phabricator.wikimedia.org/T217908 EMAIL PREFERENCES https://phabricator

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-05-17 Thread Xqt
Xqt added a comment. In T217908#5191970 , @Chicocvenancio wrote: > @Xqt do you mind rebasing that PR? or allowing me to rebase the chang

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-05-17 Thread Chicocvenancio
Chicocvenancio added a comment. @Xqt do you mind rebasing that PR? or allowing me to rebase the changes there? TASK DETAIL https://phabricator.wikimedia.org/T217908 EMAIL PREFERENCES http

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-23 Thread Chicocvenancio
Chicocvenancio added a comment. In T217908#5050483 , @Xqt wrote: > How can it be fixed? I need to investigate it. I'll create a task for it, I think it is likely a requirement not being pinned and a new version clashing with anot

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-23 Thread Xqt
Xqt added a comment. In T217908#5050328 , @Chicocvenancio wrote: > Looks good, the Travis error seems unrelated. But does mean we cannot merge yet. How can it be fixed? TASK DETAIL https://phabricator.wikimedia.org/T217908 EM

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-23 Thread Chicocvenancio
Chicocvenancio added a comment. In T217908#5050119 , @Xqt wrote: > Added a PR: https://github.com/yuvipanda/paws/pull/33 Looks good, the Travis error seems unrelated. But does mean we cannot merge yet. TASK DETAIL https://phab

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-23 Thread Xqt
Xqt added a comment. Added a PR: https://github.com/yuvipanda/paws/pull/33 TASK DETAIL https://phabricator.wikimedia.org/T217908 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Xqt Cc: zhuyifei1999, Dvorapa, pywikibot-bugs-list, Chicocvenancio, Xq

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-23 Thread Xqt
Xqt added a comment. I created the `stable` tag now TASK DETAIL https://phabricator.wikimedia.org/T217908 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Xqt Cc: zhuyifei1999, Dvorapa, pywikibot-bugs-list, Chicocvenancio, Xqt, Wenyi, R96340, Allt

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-22 Thread Dvorapa
Dvorapa added a comment. In T217908#5047370 , @Xqt wrote: > I propose another way: > Currently a new version tag like `3.0.20190301` is created every month if 5 tests passed on travis and appveyor is green. The library part is upload

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-22 Thread Xqt
Xqt added a comment. I propose another way: Currently a new version tag like `3.0.20190301` is created every month if 5 tests passed on travis and appveyor is green. The library part is uploaded to pypi then. I would create a new tag `stable` (which indicates a stable release whereas mast

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-15 Thread Dvorapa
Dvorapa added a comment. Oh I see. Then: a) $ git clone --recursive --branch $(curl pip latest version somehow?) https://gerrit.wikimedia.org/r/pywikibot/core.git b) $ git clone --recursive https://gerrit.wikimedia.org/r/pywikibot/core.git $ cd core $ git checkout

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-15 Thread zhuyifei1999
zhuyifei1999 added a comment. > $(git tag | tail -1) Need repo cloned. Seperate into two commands? TASK DETAIL https://phabricator.wikimedia.org/T217908 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Xqt, zhuyifei1999 Cc: zhuyifei1999, Dvora

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-15 Thread Dvorapa
Dvorapa added a comment. For PAWS (and we should use this way also in user docs): $ git clone --recursive --branch $(git tag | tail -1) https://gerrit.wikimedia.org/r/pywikibot/core.git TASK DETAIL https://phabricator.wikimedia.org/T217908 EMAIL PREFERENCES https://phabricator.wik

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-15 Thread Dvorapa
Dvorapa added a comment. I would personally `fetch`/`remote update` the current master and then checkout last tag (Can be found using `git tag | tail -1`) every time new tag is created, because pip package contains only library parts, not the full package, so it it not good for PAWS TASK DE

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-15 Thread Chicocvenancio
Chicocvenancio added a comment. Please document a standard, repeatable and cheap way to install and update pywikibot on PAWS. TASK DETAIL https://phabricator.wikimedia.org/T217908 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Xqt, Chicocvenanci

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-15 Thread Dvorapa
Dvorapa added a comment. That's correct. **Alternatively** ... **for active bot operators and developers** I would just reword it to **experienced bot operators and developers** as in English these two words have slightly different meaning TASK DETAIL https://phabricator.wikimedia.org/T217

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-15 Thread Chicocvenancio
Chicocvenancio added a comment. In T217908#5028025 , @Dvorapa wrote: > No, it recommends to download the code from http://tools.wmflabs.org/pywikibot/ where it is packaged both from current master and also from 1 week old master commit.

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-15 Thread Dvorapa
Dvorapa added a comment. In T217908#5019053 , @Chicocvenancio wrote: > It seems cloning from master is the recommend install method at https://www.mediawiki.org/wiki/Manual:Pywikibot/Installation No, it recommends to download the

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-12 Thread Xqt
Xqt added a comment. In T217908#5019053 , @Chicocvenancio wrote: > It seems cloning from master is the recommend install method at https://www.mediawiki.org/wiki/Manual:Pywikibot/Installation OMG no. I'll change it. TASK DETAIL

[Pywikipedia-bugs] [Maniphest] [Commented On] T217908: Don't update pywikibot directly from master but from last published tag

2019-03-12 Thread Chicocvenancio
Chicocvenancio added a comment. It seems cloning from master is the recommend install method at https://www.mediawiki.org/wiki/Manual:Pywikibot/Installation TASK DETAIL https://phabricator.wikimedia.org/T217908 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailprefe