Commits (976)

Too many changes to show.

To preserve performance only 1000 of 1000+ files are displayed.

ignore =
exclude = .git,__pycache__,.gitlab
max-complexity = 15
\ No newline at end of file
......@@ -8,18 +8,26 @@ syntax: glob
syntax: regexp
- sudo apt-get update -qq && sudo apt-get install -y -qq libtool pkg-config python3-openssl gir1.2-gtk-3.0 python3-gi python3-nbxmpp-nightly pylint3
- sudo apt-get build-dep -y -qq gajim-default-nightly
- test
- build
stage: test
- python3 setup.py test_nogui
stage: test
- pylint3 --additional-builtins=_ --disable=all --enable=E0001,E0011,E0012,E0100,E0101,E0102,E0103,E0104,E0105,E0106,E0107,E0108,E0202,E0221,E0222,E0235,E0501,E0502,E0503,E0602,E0603,E0604,E0701,E0702,E1001,E1002,E1003,E1004,E1111,E1120,E1121,E1122,E1123,E1124,E1125,E1200,E1201,E1205,E1206,E1300,E1301,E1302,E1303,E1304,E1305,E1306,E1310,E1700,E1701,W0102 gajim
stage: build
- python3 setup.py sdist
- cd dist
- export FN="gajim-default-"$(date +%F)".tar"
- mv gajim-*.tar.gz $FN.gz
- mkdir tmp_add_plugins
- mv $FN.gz tmp_add_plugins/
- cd tmp_add_plugins/
- tar xzf $FN.gz
- rm $FN.gz
- export GF=$(find . -maxdepth 1 -type d -name 'gajim-*')
- mkdir -p $GF/gajim/data/plugins/
- cd $GF/gajim/data/plugins/
- curl -O https://ftp.gajim.org/plugins_1/plugin_installer.zip
- unzip plugin_installer.zip
- rm plugin_installer.zip
- cd ../../../..
- tar czf ../$FN.gz gajim-*
- cd ..
- rm -rf tmp_add_plugins
- scp $FN.gz panoramix:/var/www/gajim/downloads/snap/ci/gajim-default-$CI_COMMIT_SHA.tar.gz
name: "gajim-default-$CI_COMMIT_REF_NAME-$CI_COMMIT_SHA"
expire_in: 1 week
- gajim-default-2???-??-??.tar.gz
**Please first check if another issue has been opened for your problem**
## Versions
- OS:
- Gajim version:
- GTK version:
- Python-nbxmpp version:
## Steps to reproduce the problem
## Expected behavior
## Actual behavior
**Please note by far the quickest way to get a new feature is to file a Merge Request.**
## Description of the new feature
Yann Leboulanger (asterix AT lagaule.org)
Philipp Hörist (philipp AT hoerist.com)
Stefan Bethge (stefan AT lanpartei.de)
Alexander Cherniuk (ts33kr AT gmail.com)
Stephan Erb (steve-e AT h3c.de)
Vincent Hanquez (tab AT snarc.org)
Dimitur Kirov (dkirov AT gmail.com)
Nikos Kouremenos (kourem AT gmail.com)
Julien Pivotto (roidelapluie AT gmail.com)
Jonathan Schleifer (js-gajim AT webkeks.org)
Travis Shirk (travis AT pobox.com)
Brendan Taylor (whateley AT gmail.com)
Jean-Marie Traissard (jim AT lapin.org)
- master - Development branch
- gajim_1.0 - Stable Gajim 1.0.x branch
- gajim_0.16 - Stable Gajim 0.16.x branch
If you are not familiar with Git please read the [HowTo](https://dev.gajim.org/gajim/gajim/wikis/howtogit)
\ No newline at end of file
Gajim 0.16.6 ( September 2016)
Gajim 1.1.0 (TBA)
* Support http:upload:0
* Support for displaying/uploading avatars for rooms
* Support for PKIX over Secure HTTP (POSH)
Gajim 1.0.2 (30 April 2018)
Bugs fixed:
* 7879 Server name is rejected for group chat bookmarks
* 8964 setup.py install misses some files if used with "--skip-build"
* 9017 Password was sometimes stored in plaintext
* 9022 Dont show error when receiving invalid avatars
* 9031 Windows: Always hide roster window on X
* 9038 No License in About dialog
* 9039 Encode filenames before sending
* 9044 Catch invalid IQ stanzas and log them
* 9049 XMPP logo in "Add New Contact" window instead Gajim logo
* 9050 Mark some strings as translatable
* 9054 Error on file send completion
* 9055 Removing a bookmark causes error
* 9057 Avatar is deleted when updating vCard
* 9065 Account label isn't change in tooltip of notification area icon
* 9066 Placeholder text does't disappear
* 9068 Missing pulseaudio in Flatpak image
* 9070 Fix History Manager search
* 9074 Proxy comobobox in accounts/connections doesn't get update after ManageProxies
* 9094 problem receiving file
* 9101 Notification never autohides in gnome
* Correctly reload Plugins
* Save history export with utf8 encoding
* Dont allow plain BOSH by default
Gajim 1.0.1 (1 April 2018)
* Improve MAM support
* Image preview in file chooser dialog
* Groupchat: Set minimize on auto join default True
* Delete bookmark when we destroy a room
* Fix account deletion
* Fix custom font handling
* Fix OpenPGP message decryption
* Fix window position restore on multi-head setups
* Fix scrolling in message window
* Improve Windows build and build for 64 bits
Gajim 1.0.0 (17 March 2018)
* Ported to GTK3 / Python3
* Integrate HTTPUpload
* Add Navigation buttons in History Window
* Improvements for HiDPI Screens
* Depend on the python keyring package for password storage
* Flatpak support
* Lots of refactoring
* New Emoji support
* New Chat Window design
* New StartChat Window (Ctrl+N)
* New ServerInfo Window
* AccountWindow Redesign
* Moved some encryption code out into Plugins (see PGP Plugin, Esessions Plugin)
* OTR Plugin was not ported, use OMEMO
* Added mam:1 and mam:2 support (mam:0 was removed)
* Added MAM for MUCs support
* Added support for showing XEP-0084 Avatars
* Add support for geo: URIs
* Added xmpp URI handling directly in Gajim
* Removed Gajim-Remote
* Removed XEP-0012 (Last Activity)
* Removed XEP-0136 (Message Archiving)
* Added XEP-0156 (Discovering Alternative XMPP Connection Methods)
* Added XEP-0319 (Last User Interaction in Presence)
* Added XEP-0368 (SRV records for XMPP over TLS)
* Added XEP-0380 (Explicit Message Encryption)
* Added Jingle FT:5 support
* Lots of other small bugfixes
- Meta Contacts: Filtering the roster could lead to a crash in some circumstances. Use CTRL + N for starting new chats as a workaround
- Audio/Video support is currently not maintained and most likely not working
- Windows: Translation is not working currently
Gajim 0.16.9 (30 November 2017)
* Improve Zeroconf behavior
* Fix showing normal message event
* remove usage of OpenSSL.rand
* a few minor bugfixes
Gajim 0.16.8 (04 June 2017)
* Fix rejoining MUCs after connection loss
* Fix Groupchat invites
* Fix encoding problems with newer GnuPG versions
* Fix old messages randomly reappearing in the chat window
* Fix some problems with IBB filetransfer
* Make XEP-0146 Commands opt-in
* Improve sending messages to your own resources
* Improve reliability of delivery recipes
* Many minor bugfixes
Gajim 0.16.7 (30 January 2017)
* Better compatibility with XEP-0191: Blocking Command
* Windows Credential Vault is used for password storage on Windows
* Gajim now depends on python-gnupg for PGP encryption
* Add portable installer for Windows
* Remove usage of demandimport
* Many minor bugfixes
Gajim 0.16.6 (02 October 2016)
* Fix using gpg2
* Improve message receips usage
* Improve message receipts usage
* Improve roster filtering
* several minor bugs
Installation Instructions
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
Basic Installation
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You only need
`configure.ac' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
Some systems require unusual options for compilation or linking that the
`configure' script does not know about. Run `./configure --help' for
details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory. After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.
Installation Names
By default, `make install' installs the package's commands under
`/usr/local/bin', include files under `/usr/local/include', etc. You
can specify an installation prefix other than `/usr/local' by giving
`configure' the option `--prefix=PREFIX'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
PREFIX as the prefix for installing programs and libraries.
Documentation and other data files still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
There may be some features `configure' cannot figure out automatically,
but needs to determine by the type of machine the package will run on.
Usually, assuming the package is built to be run on the _same_
architectures, `configure' can figure that out, but if it prints a
message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
where SYSTEM can have one of these forms:
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the option `--target=TYPE' to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Sharing Defaults
If you want to set default values for `configure' scripts to share, you
can create a site shell script called `config.site' that gives default
values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Defining Variables
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script). Here is a another example:
/bin/bash ./configure CONFIG_SHELL=/bin/bash
Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
configuration-related scripts to be executed by `/bin/bash'.
`configure' Invocation
`configure' recognizes the following options to control how it operates.
Print a summary of the options to `configure', and exit.
Print the version of Autoconf used to generate the `configure'
script, and exit.
Enable the cache: use and save the results of the tests in FILE,