Folks, I really made a lot of effort, even asked somebody to help IRL, but I am tired.
I want develop Pywikibot, instead I am struggling with the working environment. Although git is hundred times as complicated as SVN and gerrit is a nightmare, my main problem is with git installing i18n submodule. See https://phabricator.wikimedia.org/T329452
It causes two main problems:
- I cannot run tests. I have another copy of Pywikibot from downloaded zip, I can run tests there, but the same command fails in git copy. - I cannot push my commits. For some reason an i18n part is always included which makes Jenkins fail. Now I can remove it after pushing, but Jenkins fails again, see https://gerrit.wikimedia.org/r/c/pywikibot/core/+/888745
Error message: https://integration.wikimedia.org/ci/job/pywikibot-core-tox-doctest-docker/7... : FAILURE in 33s I am very frustrated and disappointed, but I cannot do anything until T329452 is solved somehow.
Hi Bináris
Can you perhaps push from your toolforge user directory? [1] As a workaround, something like this might work for you.
1. Download the pywikibot zip to your local environment. Apparently it's Windows in your case, but it can be anything. 2. Make changes to the files. I assume you can run tests as well. 3. Use ssh to login to toolforge, and use git clone to setup a clone of the pywikibot git repository in your toolforge user directory. 4. Copy the locally changed files to your toolforge user directory. (Use a rsync or sftp client.) 5. Back to the toolforge shell, commit the changes to the repository in your toolforge user directory, and push using git review.
[1] https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Quickstart
# I see the linked phabricator ticket was declined because the discussion was getting out of scope. I hope this one last message helps. Otherwise, we probably shouldn't continue talking about individual setups here as well.
-Yusuke (User:Whym)
On Wed, Feb 15, 2023 at 8:19 PM Bináris wikiposta@gmail.com wrote:
Folks, I really made a lot of effort, even asked somebody to help IRL, but I am tired.
I want develop Pywikibot, instead I am struggling with the working environment. Although git is hundred times as complicated as SVN and gerrit is a nightmare, my main problem is with git installing i18n submodule. See https://phabricator.wikimedia.org/T329452
It causes two main problems:
I cannot run tests. I have another copy of Pywikibot from downloaded zip, I can run tests there, but the same command fails in git copy. I cannot push my commits. For some reason an i18n part is always included which makes Jenkins fail. Now I can remove it after pushing, but Jenkins fails again, see https://gerrit.wikimedia.org/r/c/pywikibot/core/+/888745
Error message: https://integration.wikimedia.org/ci/job/pywikibot-core-tox-doctest-docker/7... : FAILURE in 33s I am very frustrated and disappointed, but I cannot do anything until T329452 is solved somehow.
-- Bináris _______________________________________________ pywikibot mailing list -- pywikibot@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/me... To unsubscribe send an email to pywikibot-leave@lists.wikimedia.org
Thank you for the idea! This sounds interesting. But I would have to upload my private key to Toolforge, which sounds bad, wouldn't I?
Yusuke Matsubara whym@whym.org ezt írta (időpont: 2023. febr. 20., H, 12:48):
Hi Bináris
Can you perhaps push from your toolforge user directory? [1] As a workaround, something like this might work for you.
- Download the pywikibot zip to your local environment. Apparently
it's Windows in your case, but it can be anything. 2. Make changes to the files. I assume you can run tests as well. 3. Use ssh to login to toolforge, and use git clone to setup a clone of the pywikibot git repository in your toolforge user directory. 4. Copy the locally changed files to your toolforge user directory. (Use a rsync or sftp client.) 5. Back to the toolforge shell, commit the changes to the repository in your toolforge user directory, and push using git review.
[1] https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Quickstart
# I see the linked phabricator ticket was declined because the discussion was getting out of scope. I hope this one last message helps. Otherwise, we probably shouldn't continue talking about individual setups here as well.
-Yusuke (User:Whym)
On Wed, Feb 15, 2023 at 8:19 PM Bináris wikiposta@gmail.com wrote:
Folks, I really made a lot of effort, even asked somebody to help IRL,
but I am tired.
I want develop Pywikibot, instead I am struggling with the working
environment. Although git is hundred times as complicated as SVN and gerrit is a nightmare, my main problem is with git installing i18n submodule.
See https://phabricator.wikimedia.org/T329452
It causes two main problems:
I cannot run tests. I have another copy of Pywikibot from downloaded
zip, I can run tests there, but the same command fails in git copy.
I cannot push my commits. For some reason an i18n part is always
included which makes Jenkins fail. Now I can remove it after pushing, but Jenkins fails again, see https://gerrit.wikimedia.org/r/c/pywikibot/core/+/888745
Error message:
https://integration.wikimedia.org/ci/job/pywikibot-core-tox-doctest-docker/7... : FAILURE in 33s
I am very frustrated and disappointed, but I cannot do anything until
T329452 is solved somehow.
-- Bináris _______________________________________________ pywikibot mailing list -- pywikibot@lists.wikimedia.org Public archives at
https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/me...
To unsubscribe send an email to pywikibot-leave@lists.wikimedia.org
pywikibot mailing list -- pywikibot@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/me... To unsubscribe send an email to pywikibot-leave@lists.wikimedia.org
info@gno.de ezt írta (időpont: 2023. febr. 20., H, 18:20):
… Sorry the mail was committed by accident…
Anyway I would like to recommend TortoiseGit. I’ve wrote a documentation at mediawiki wiki how to use it.
Maybe we can organize an online meeting to introduce this way or I could help remote via TeamViewer. How do you find my proposals, how should we proceed?
Yes, absolutely! I will be very grateful for your help! You already spoke me about Tortoisegit, so I gave it a chance, but the error message was the same as in command line git. In Phabricator you may see how many ideas I got from people, and none of them helped. Theoretically I cannot interpret the situation that a 500 server error occurs just for me, because either there is a server error or not, and 500 means internal error, not client side.
So yes, I ask your help!
I've used a few VCS's in my time. Unless I've forgotten something, RCS, CVS, SVN, ClearCase, Perforce, hg, and most recently git. I can't argue that git is complicated. Probably more complicated than most people need.
On Feb 20, 2023, at 12:11 PM, info@gno.de wrote:
Hi Binaris,
I am with you that gerrit is much more difficult to handle than svn. I remember that bad time after the switch and I had to make a lot of tries and errors and I was about to give up and leave the project.
As we met us in Berlin decades ago I think you also was a Windows user and I thought that you was more familiar with git/gerrit than I was it that date.
Anyway I have found a nice way to contribute to the gerrit repository: The magic is TortoiseGit, easy to use, graphic UI and some useful
Am 20.02.2023 um 14:20 schrieb Bináris wikiposta@gmail.com:
Thank you for the idea! This sounds interesting. But I would have to upload my private key to Toolforge, which sounds bad, wouldn't I?
Yusuke Matsubara <whym@whym.org mailto:whym@whym.org> ezt írta (időpont: 2023. febr. 20., H, 12:48): Hi Bináris
Can you perhaps push from your toolforge user directory? [1] As a workaround, something like this might work for you.
- Download the pywikibot zip to your local environment. Apparently
it's Windows in your case, but it can be anything. 2. Make changes to the files. I assume you can run tests as well. 3. Use ssh to login to toolforge, and use git clone to setup a clone of the pywikibot git repository in your toolforge user directory. 4. Copy the locally changed files to your toolforge user directory. (Use a rsync or sftp client.) 5. Back to the toolforge shell, commit the changes to the repository in your toolforge user directory, and push using git review.
[1] https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Quickstart https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Quickstart
# I see the linked phabricator ticket was declined because the discussion was getting out of scope. I hope this one last message helps. Otherwise, we probably shouldn't continue talking about individual setups here as well.
-Yusuke (User:Whym)
On Wed, Feb 15, 2023 at 8:19 PM Bináris <wikiposta@gmail.com mailto:wikiposta@gmail.com> wrote:
Folks, I really made a lot of effort, even asked somebody to help IRL, but I am tired.
I want develop Pywikibot, instead I am struggling with the working environment. Although git is hundred times as complicated as SVN and gerrit is a nightmare, my main problem is with git installing i18n submodule. See https://phabricator.wikimedia.org/T329452 https://phabricator.wikimedia.org/T329452
It causes two main problems:
I cannot run tests. I have another copy of Pywikibot from downloaded zip, I can run tests there, but the same command fails in git copy. I cannot push my commits. For some reason an i18n part is always included which makes Jenkins fail. Now I can remove it after pushing, but Jenkins fails again, see https://gerrit.wikimedia.org/r/c/pywikibot/core/+/888745 https://gerrit.wikimedia.org/r/c/pywikibot/core/+/888745
Error message: https://integration.wikimedia.org/ci/job/pywikibot-core-tox-doctest-docker/7... https://integration.wikimedia.org/ci/job/pywikibot-core-tox-doctest-docker/7631/console : FAILURE in 33s I am very frustrated and disappointed, but I cannot do anything until T329452 is solved somehow.
-- Bináris _______________________________________________ pywikibot mailing list -- pywikibot@lists.wikimedia.org mailto:pywikibot@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/me... https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/message/MQWDKSWS5LBBEZ4LHOMGAZRKFG3O7OZM/ To unsubscribe send an email to pywikibot-leave@lists.wikimedia.org mailto:pywikibot-leave@lists.wikimedia.org
pywikibot mailing list -- pywikibot@lists.wikimedia.org mailto:pywikibot@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/me... https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/message/QLKUHZGPT4FCVE54ZVR7VSBMOE43VIE6/ To unsubscribe send an email to pywikibot-leave@lists.wikimedia.org mailto:pywikibot-leave@lists.wikimedia.org
-- Bináris _______________________________________________ pywikibot mailing list -- pywikibot@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/me... To unsubscribe send an email to pywikibot-leave@lists.wikimedia.org
pywikibot mailing list -- pywikibot@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/me... To unsubscribe send an email to pywikibot-leave@lists.wikimedia.org
Ooops, hit send too soon.
The rest of what I wanted to say was that, for better or worse, git has won, at least now. Looking for client applications that make it easier to use is a good thing, but I hope nobody is thinking of moving to some other VCS for the underlying repository and protocol.
On Feb 20, 2023, at 12:21 PM, Roy Smith roy@panix.com wrote:
I've used a few VCS's in my time. Unless I've forgotten something, RCS, CVS, SVN, ClearCase, Perforce, hg, and most recently git. I can't argue that git is complicated. Probably more complicated than most people need.
On Feb 20, 2023, at 12:11 PM, info@gno.de mailto:info@gno.de wrote:
Hi Binaris,
I am with you that gerrit is much more difficult to handle than svn. I remember that bad time after the switch and I had to make a lot of tries and errors and I was about to give up and leave the project.
As we met us in Berlin decades ago I think you also was a Windows user and I thought that you was more familiar with git/gerrit than I was it that date.
Anyway I have found a nice way to contribute to the gerrit repository: The magic is TortoiseGit, easy to use, graphic UI and some useful
Am 20.02.2023 um 14:20 schrieb Bináris <wikiposta@gmail.com mailto:wikiposta@gmail.com>:
Thank you for the idea! This sounds interesting. But I would have to upload my private key to Toolforge, which sounds bad, wouldn't I?
Yusuke Matsubara <whym@whym.org mailto:whym@whym.org> ezt írta (időpont: 2023. febr. 20., H, 12:48): Hi Bináris
Can you perhaps push from your toolforge user directory? [1] As a workaround, something like this might work for you.
- Download the pywikibot zip to your local environment. Apparently
it's Windows in your case, but it can be anything. 2. Make changes to the files. I assume you can run tests as well. 3. Use ssh to login to toolforge, and use git clone to setup a clone of the pywikibot git repository in your toolforge user directory. 4. Copy the locally changed files to your toolforge user directory. (Use a rsync or sftp client.) 5. Back to the toolforge shell, commit the changes to the repository in your toolforge user directory, and push using git review.
[1] https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Quickstart https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Quickstart
# I see the linked phabricator ticket was declined because the discussion was getting out of scope. I hope this one last message helps. Otherwise, we probably shouldn't continue talking about individual setups here as well.
-Yusuke (User:Whym)
On Wed, Feb 15, 2023 at 8:19 PM Bináris <wikiposta@gmail.com mailto:wikiposta@gmail.com> wrote:
Folks, I really made a lot of effort, even asked somebody to help IRL, but I am tired.
I want develop Pywikibot, instead I am struggling with the working environment. Although git is hundred times as complicated as SVN and gerrit is a nightmare, my main problem is with git installing i18n submodule. See https://phabricator.wikimedia.org/T329452 https://phabricator.wikimedia.org/T329452
It causes two main problems:
I cannot run tests. I have another copy of Pywikibot from downloaded zip, I can run tests there, but the same command fails in git copy. I cannot push my commits. For some reason an i18n part is always included which makes Jenkins fail. Now I can remove it after pushing, but Jenkins fails again, see https://gerrit.wikimedia.org/r/c/pywikibot/core/+/888745 https://gerrit.wikimedia.org/r/c/pywikibot/core/+/888745
Error message: https://integration.wikimedia.org/ci/job/pywikibot-core-tox-doctest-docker/7... https://integration.wikimedia.org/ci/job/pywikibot-core-tox-doctest-docker/7631/console : FAILURE in 33s I am very frustrated and disappointed, but I cannot do anything until T329452 is solved somehow.
-- Bináris _______________________________________________ pywikibot mailing list -- pywikibot@lists.wikimedia.org mailto:pywikibot@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/me... https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/message/MQWDKSWS5LBBEZ4LHOMGAZRKFG3O7OZM/ To unsubscribe send an email to pywikibot-leave@lists.wikimedia.org mailto:pywikibot-leave@lists.wikimedia.org
pywikibot mailing list -- pywikibot@lists.wikimedia.org mailto:pywikibot@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/me... https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/message/QLKUHZGPT4FCVE54ZVR7VSBMOE43VIE6/ To unsubscribe send an email to pywikibot-leave@lists.wikimedia.org mailto:pywikibot-leave@lists.wikimedia.org
-- Bináris _______________________________________________ pywikibot mailing list -- pywikibot@lists.wikimedia.org mailto:pywikibot@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/me... https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/message/RB3QT4VOE3ULBQWW6L3MA7CB77AMYRZF/ To unsubscribe send an email to pywikibot-leave@lists.wikimedia.org mailto:pywikibot-leave@lists.wikimedia.org
pywikibot mailing list -- pywikibot@lists.wikimedia.org mailto:pywikibot@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/me... https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/message/BYWHZ3RI7LVXKXOFCMHU3C2WPOMH5VR3/ To unsubscribe send an email to pywikibot-leave@lists.wikimedia.org mailto:pywikibot-leave@lists.wikimedia.org
Roy Smith roy@panix.com ezt írta (időpont: 2023. febr. 20., H, 18:24):
The rest of what I wanted to say was that, for better or worse, git has won, at least now. Looking for client applications that make it easier to use is a good thing, but I hope nobody is thinking of moving to some other VCS for the underlying repository and protocol.
I am not a dreamer, I know that SVN is dead, and if I want to do anything with programming in 2023, I have to go on with git. That would be OK. More problem is with gerrit. I know that some folks want to move to Gitlab, but there is no deadline, and I don't want to wait some more years. I didn't vote for gerrit when we had the choice on this list, but the majority voted for moving together with MediaWiki developers. That is still OK. The main issue is this strange and mystic error with pulling i18n submodule. Google is not my friend, I tried everything that I found on Stackoverflow, and nothing hepls.
For several years I maintained compat/trunk on my computer, developed scripts for myself. But last year sysops decided to throw out every bot for some security problem, and by that time login didn't work any more, so I couldn't go on. Now I was forced to get know the core, and I will have tremendous work with replace.py until it will have the same knowledge for me. Once I have to do this, I want to do for everybody, so that other people can use my developments and I don't have to maintain a whole personal branch. :-) That is my life story. :-)
Thank you for the idea! This sounds interesting. But I would have to upload my private key to Toolforge, which sounds bad, wouldn't I?
I only meant to say it could be a temporary workaround, and you probably shouldn't upload a key you are already using somewhere else. There are measures you can take, like hiding it using file permissions, using a new key and making sure you don't reuse it anywhere else, deleting the key once you sort it out with other methods. Still, I agree that some risks would remain in a shared environment like toolforge.
-Yusuke (User:Whym)
On Mon, Feb 20, 2023 at 10:20 PM Bináris wikiposta@gmail.com wrote:
Thank you for the idea! This sounds interesting. But I would have to upload my private key to Toolforge, which sounds bad, wouldn't I?
Yusuke Matsubara whym@whym.org ezt írta (időpont: 2023. febr. 20., H, 12:48):
Hi Bináris
Can you perhaps push from your toolforge user directory? [1] As a workaround, something like this might work for you.
- Download the pywikibot zip to your local environment. Apparently
it's Windows in your case, but it can be anything. 2. Make changes to the files. I assume you can run tests as well. 3. Use ssh to login to toolforge, and use git clone to setup a clone of the pywikibot git repository in your toolforge user directory. 4. Copy the locally changed files to your toolforge user directory. (Use a rsync or sftp client.) 5. Back to the toolforge shell, commit the changes to the repository in your toolforge user directory, and push using git review.
[1] https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Quickstart
# I see the linked phabricator ticket was declined because the discussion was getting out of scope. I hope this one last message helps. Otherwise, we probably shouldn't continue talking about individual setups here as well.
-Yusuke (User:Whym)
On Wed, Feb 15, 2023 at 8:19 PM Bináris wikiposta@gmail.com wrote:
Folks, I really made a lot of effort, even asked somebody to help IRL, but I am tired.
I want develop Pywikibot, instead I am struggling with the working environment. Although git is hundred times as complicated as SVN and gerrit is a nightmare, my main problem is with git installing i18n submodule. See https://phabricator.wikimedia.org/T329452
It causes two main problems:
I cannot run tests. I have another copy of Pywikibot from downloaded zip, I can run tests there, but the same command fails in git copy. I cannot push my commits. For some reason an i18n part is always included which makes Jenkins fail. Now I can remove it after pushing, but Jenkins fails again, see https://gerrit.wikimedia.org/r/c/pywikibot/core/+/888745
Error message: https://integration.wikimedia.org/ci/job/pywikibot-core-tox-doctest-docker/7... : FAILURE in 33s I am very frustrated and disappointed, but I cannot do anything until T329452 is solved somehow.
-- Bináris _______________________________________________ pywikibot mailing list -- pywikibot@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/me... To unsubscribe send an email to pywikibot-leave@lists.wikimedia.org
pywikibot mailing list -- pywikibot@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/me... To unsubscribe send an email to pywikibot-leave@lists.wikimedia.org
-- Bináris _______________________________________________ pywikibot mailing list -- pywikibot@lists.wikimedia.org Public archives at https://lists.wikimedia.org/hyperkitty/list/pywikibot@lists.wikimedia.org/me... To unsubscribe send an email to pywikibot-leave@lists.wikimedia.org