Manual talk:Pywikibot/Gerrit

Outdated framework
Hi there,

I'm not running a bot, but I'm concerned of bots not switching to Git. How can it be managed that there are no bots operating with outdated framework?

--Murma174 (talk) 14:42, 23 July 2013 (UTC) (Sysop and Crat on frrwiki)
 * Hi, I think you got wrong. A bot operator usually uses this command to update their code (usually it's done automatically):

but after this migration this command won't work anymore and running this command won't cause updating of codes, so a bot op has to switch commands and specially update command in order to be able receive new patches Ladsgroup (talk) 16:20, 23 July 2013 (UTC)
 * I think there is a problem because at one point there will come an important update and then there will be a bot war between the updated bots and the bots that are still running the old code. That is not a problem with git or svn, but with simply outdated bots. Most of the admins and stewards are aware of this rare problem and knows what to do. Carsrac (talk) 15:49, 4 August 2013 (UTC)
 * I just did a update via svn and it works so I don't understand what all the fuss is about that "svn update" does not work anymore :) Carsrac (talk) 15:54, 4 August 2013 (UTC)
 * Personally, I never update my Pywikipedia version. The date of my most recent Pywikipedia files is 10/04/2010. I see no reason to update, as my bots work correctly. Is there an imperative reason to do something in my case? Lmaltier (talk) 20:18, 23 July 2013 (UTC)
 * Updating codes are very important because mediawiki changes and sometimes these changes are critical and if you don't update your codes maybe your bot crashes and I'm sure you use your bot in very narrow field. try to run other codes. Ladsgroup (talk) 20:31, 23 July 2013 (UTC)
 * Sure, I don't use much of Pywikipedia: my bots are based on template.php only (and, indirectly, on files this program calls). What is important to me is that this part never breaks (or, at least, to know what to do if some change requires an action). Is this such a case? Lmaltier (talk) 20:52, 23 July 2013 (UTC)
 * SVN is still available, but in a read only state. However, if there is a good reason to block the bot, we can always ask the WMF to temporarily allow write access, so we can add a 'blocking' commit. Valhallasw (talk) 08:05, 22 August 2013 (UTC)

Adding "--recursive" for other git users
We didn't suggest this option to ordinary (not hackers) users. It's a very good and there is no need to do so many stuff (fetching and other things) and I think It's good to suggest it to clinets too so What do you think? 12:54, 20 August 2013 (UTC)

Gerrit -> Phabricator
It appears the repo moved from Gerrit to Phabricator and is now located here: https : //phabricator. wikimedia. org/diffusion/PWBC/ (Remove spaces. I can't post a URL.)

section 3.1 : reference to v1.18 missing anchor
In "any version like 1.12, 1.21, but NOT v1.18" where v1.18 is NOT v1.18 anchor does not exist on the target page.

Christian 🇫🇷 FR (talk) 13:01, 26 May 2021 (UTC)


 * Text disappears here => https://www.mediawiki.org/w/index.php?title=Gerrit/git-review&diff=next&oldid=2116759
 * substitued by "For problems and how to solve them, see Gerrit/Troubleshooting."
 * There "set change:62474" is referred in https://www.mediawiki.org/wiki/Gerrit/Troubleshooting
 * at §3.4 git-review complains "Cannot query patchset information"
 * so defining there
 * and referencing it here as Gerrit/Troubleshooting

Christian 🇫🇷 FR (talk) 13:46, 26 May 2021 (UTC)

expired certificate?
I'm trying to update my bot to the latest pywikibot. Rather than update I thought I'd just install from scratch. Here's what I get: The issue the bot is getting might also be expired certificates. Is someone working on this?

--en:user:Rick Block 01:17, 19 October 2021 (UTC)
 * This is probably related to HTTPS/2021 Let's Encrypt root expiry * Pppery * it has begun 01:44, 19 October 2021 (UTC)