Gajim-devel December 2016

gajim-devel@gajim.org

5 participants
7 discussions

Issues with migration from trac/mercurial to gitlab/git
by Andrey Gursky 31 Dec '16

31 Dec '16

Hi, a couple of days ago I noticed, that mercurial repository has gone. But no replacement was setup. I haven't found any announcement here on the list about the migration. Couldn't you switch it just into read-only mode, which is already the only possible way to access the server for everybody except developers? The old trac has gone either. What do you think about an archive read-only mode access? Let's look at https://dev.gajim.org/gajim/gajim/issues/8390 It has been filed by anonymous. Can this be true? Did old trac allow anonymous accounts (without at least partly anonymezed email reference)? Looking further at the comment: https://dev.gajim.org/gajim/gajim/issues/8390#note_137507 a changeset is mentioned: In [changeset:"849a745fc6c17d18626b480d4ed7d3844be8280e" 16114:849a745fc6c1] But I can't click on it to be forwarded to the actual commit. Hopefully, you can fix that? For example here https://dev.gajim.org/gajim/python-nbxmpp/issues/20 The issues and commits references are correctly linked. Let's look at https://dev.gajim.org/gajim/gajim/issues/8266 Again, an anonymous has supplied a patch. But the patch looks like to be linked to Thilo Molitor's post. And in the commit https://dev.gajim.org/gajim/gajim/commit/766bb508e323f849d it seems the author is someone with nick gdr_gdr. But despite of the commit comment "Fixes # 8266" the issue remained open. Moreover, due to the space between # and 8266 gitlab cannot replace it with a proper hyperlink. Maybe that is the reason for the stale status of the issue? To check such issues, a read-only archive mode access to old trac would be helpful. Now let's look how much space the old mercurial repository occupies: $ du -sh .hg 80M .hg Let's clone the new repository: $ date Tue Dec 6 19:45:46 CET 2016 $ git clone https://dev.gajim.org/gajim/gajim.git gajim.git Cloning into 'gajim.git'... remote: Counting objects: 93373, done. remote: Compressing objects: 100% (27957/27957), done. remote: Total 93373 (delta 63116), reused 93357 (delta 63105) Receiving objects: 100% (93373/93373), 432.84 MiB | 5.52 MiB/s, done. Resolving deltas: 100% (63116/63116), done. Checking connectivity... done. $ du -sh gajim.git/.git 436M gajim.git/.git $ That's really very much data. Please run git gc --aggressive on the repository to avoid wasted traffic and doing this by everyone who clones the repository: $ du -sm .git; git gc --aggressive; du -sm .git 436 .git Counting objects: 93373, done. Compressing objects: 100% (91048/91048), done. Writing objects: 100% (93373/93373), done. Total 93373 (delta 70902), reused 18994 (delta 0) 35 .git $ 436 --> 35 MB, not bad (it took 2 min 25 sec on a 5 year old laptop)! And efficiently than mercurial. Similar with gajim-plugins. It would be great, if you could enable git:// access to the repositories. Those were my first impressions. Thanks for your attention, Andrey

2 12

gajim-plugins git development integration into gajim git
by Andrey Gursky 18 Dec '16

18 Dec '16

Hi, to test and be able to commit changes at one place, plugins git could be placed into gajim git directory and included into .gitignore. But there is already plugins dir in gajim. So what is a git flow for plugins development? Since I'm using another profile for debug purposes, if I copy gajim-plugins git as ~/.local/share/gajim/plugins, this affects also my "stable" gajim. Is there something similar for plugins (using plugins.test for profile "test")? Regards, Andrey

2 2

Running 2 gajim instances simultaneously
by Andrey Gursky 16 Dec '16

16 Dec '16

Hi, I'm debugging file transfer now and I'd need to run a second instance of Gajim simultaneously. Is it enough to point the environment variables $XDG_CACHE_DIR, $XDG_CONFIG_DIR and $XDG_DATA_DIR to other than default path to achieve this? Thanks, Andrey

2 2

Accepting new server certificate
by Alex Malmyguine 14 Dec '16

14 Dec '16

Is it normal that a new certificate has to be accepted 3 times? First time the users get an error dialog with no check boxes. After they go off and back online, they are presented with another error dialog, which has 2 check boxes: to ignore the error and accept certificate. After they go off and back online again, they get the 3d dialog, this time with one check box to accept the cert.

2 7

Windows 8.1 user
by Alex Malmyguine 13 Dec '16

13 Dec '16

Of all the users on my XMPP servers, only one uses Gajim 0.16.5 under Windows 8.1 64bit And this one user only has the issue. When the others chat with that user, the outgoing messages often get flagged with red X for quite some time. That user receives the messages and replies to them, but their peers still see their sent messages with a red X instead of a green check mark. This is somewhat annoying, as when they send a message, they do not know why that user is not responding - because they never received the message, or because they are not at their desk. No one else who use Windows 7, XP or Linux ever had this issue. Anything we can fix in Gajim or Windows 8.1 settings or on the XMPP server for this? Thanks Alex

2 2

0.16.5 cannot re-connect to a server after the server experienced high packet loss kind of outage
by Alex Malmyguine 13 Dec '16

13 Dec '16

For the last few days my server's ISP had issues with 80-90% packet loss. Gajim disconnected every time and could not re-connect on its own. The users could not get a connection no matter how many times the users used offline and online menu. Only after closing Gajim completely and re-starting it, they were able to connect. Should Gajim not re-connect automatically?

2 1

trac rejects followup comment | #8347 support kwallet-query
by azrdev＠qrdn.de 01 Dec '16

01 Dec '16

Hi, I'd like to add a followup comment to my trac issue <>, but trac won't let me telling SpamBayes probability were 99,sth % The comment: @asterix: cool that things are happening! Do I understand correctly that you're dropping support for kwalletcli (i.e. the KDE4 implementation) completely, which leaves us compatible with gnome and KDE 5 only? Also, please consider adapting my 03_migration.patch and integrating it: Avoiding to have the migrations between backends will make the code better maintainable (imagine anyone adding another backend, again). Also, it makes it easy to ensure passwords are removed from an old backend after migration. azrdev

3 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Gajim-devel December 2016