git-cola: The highly caffeinated Git GUI

Overview

git-cola: The highly caffeinated Git GUI

git-cola is a powerful Git GUI with a slick and intuitive user interface.

Copyright (C) 2007-2020, David Aguilar and contributors

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see <http://www.gnu.org/licenses/>.

SCREENSHOTS

Screenshots are available on the git-cola screenshots page.

DOWNLOAD

apt install git-cola

New releases are available on the git-cola download page.

FORK

git clone git://github.com/git-cola/git-cola.git

git-cola build status

git-cola on github

git-cola google group

NUTRITIONAL FACTS

ACTIVE INGREDIENTS

  • git 1.6.3 or newer.

  • Python 2.6 or newer (Python 2+3 compatible).

  • QtPy 1.1.0 or newer.

  • argparse 1.1 or newer. argparse is part of the stdlib in Python 2.7; install argparse separately if you are running on Python 2.6.

  • Sphinx for building the documentation.

git-cola uses QtPy, so you can choose between PyQt4, PyQt5, and PySide by setting the QT_API environment variable to pyqt4, pyqt5 or pyside as desired. qtpy defaults to pyqt5 and falls back to pyqt4 if pyqt5 is not installed.

Any of the following Python Qt libraries must be installed:

Set QT_API=pyqt4 in your environment if you have both versions of PyQt installed and want to ensure that PyQt4 is used.

ADDITIVES

git-cola enables additional features when the following Python modules are installed.

send2trash enables cross-platform "Send to Trash" functionality.

BREWING INSTRUCTIONS

RUN FROM SOURCE

You don't need to install git-cola to run it. Running git-cola from its source tree is the easiest way to try the latest version.

git clone git://github.com/git-cola/git-cola.git
cd git-cola
./bin/git-cola
./bin/git-dag

You can also start cola as a Python module if Python can find it.

cd git-cola
python -m cola
python -m cola dag

Having git-cola's bin/ directory in your path allows you to run git cola like a regular built-in Git command:

# Replace "$PWD/bin" with the path to git-cola's bin/ directory
PATH="$PWD/bin":"$PATH"
export PATH

git cola
git dag

The instructions below assume that you have git-cola present in your $PATH. Replace "git cola" with "./bin/git-cola" as needed if you'd like to just run it in-place.

DOCUMENTATION

INSTALLATION

Normally you can just do "make install" to install git-cola in your $HOME directory ($HOME/bin, $HOME/share, etc). If you want to do a global install you can do

make prefix=/usr install

The platform-specific installation methods below use the native package manager. You should use one of these so that all of git-cola's dependencies are installed.

Distutils is used by the Makefile via setup.py to install git-cola and its launcher scripts. distutils replaces the #!/usr/bin/env python lines in scripts with the full path to python at build time, which can be undesirable when the runtime python is not the same as the build-time python. To disable the replacement of the #!/usr/bin/env python lines, pass USE_ENV_PYTHON=1 to make.

LINUX

Linux is it! Your distro has probably already packaged git-cola. If not, please file a bug against your distribution ;-)

arch

Available in the AUR.

debian, ubuntu

apt install git-cola

fedora

dnf install git-cola

gentoo

emerge git-cola

opensuse, sle

zypper install git-cola

slackware

Available in SlackBuilds.org.

FreeBSD

# install from official binary packages
pkg install -r FreeBSD devel/git-cola
# build from source
cd /usr/ports/devel/git-cola && make clean install

Ubuntu

The default version on 18.04 is older and is missing features and enhancements. Use this PPA maintained by @pavreh to get a newer version.

MAC OS X

Homebrew is the easiest way to install git-cola's Qt4 and PyQt4 dependencies. We will use Homebrew to install the git-cola recipe, but build our own .app bundle from source.

Sphinx is used to build the documentation.

brew install sphinx-doc
brew install git-cola

Once brew has installed git-cola you can:

  1. Clone git-cola

    git clone git://github.com/git-cola/git-cola.git && cd git-cola

  2. Build the git-cola.app application bundle

    make \
        PYTHON=$(brew --prefix python3)/bin/python3 \
        PYTHON_CONFIG=$(brew --prefix python3)/bin/python3-config \
        SPHINXBUILD=$(brew --prefix sphinx-doc)/bin/sphinx-build \
        git-cola.app
    
  3. Copy it to /Applications

    rm -fr /Applications/git-cola.app && cp -r git-cola.app /Applications

Newer versions of Homebrew install their own python3 installation and provide the PyQt5 modules for python3 only. You have to use python3 ./bin/git-cola when running from the source tree.

UPGRADING USING HOMEBREW

If you upgrade using brew then it is recommended that you re-install git-cola's dependencies when upgrading. Re-installing ensures that the Python modules provided by Homebrew will be properly set up.

This is required when upgrading to a modern (post-10.11 El Capitan) Mac OS X. Homebrew now bundles its own Python3 installation instead of using the system-provided default Python.

# update homebrew
brew update

# uninstall git-cola and its dependencies
brew uninstall git-cola
brew uninstall pyqt5
brew uninstall sip

# re-install git-cola and its dependencies
brew install git-cola

WINDOWS INSTALLATION

IMPORTANT If you have a 64-bit machine, install the 64-bit versions only. Do not mix 32-bit and 64-bit versions.

Download and install the following:

Once these are installed you can run Git Cola from the Start menu.

See "WINDOWS (continued)" below for more details.

GOODIES

git cola ships with an interactive rebase editor called git-cola-sequence-editor. git-cola-sequence-editor is used to reorder and choose commits when rebasing. Start an interactive rebase through the "Rebase" menu, or through the git cola rebase sub-command to use the git-cola-sequence-editor:

git cola rebase origin/main

git-cola-sequence-editor can be launched independently of git cola by telling git rebase to use it as its editor through the GIT_SEQUENCE_EDITOR enviironment variable:

env GIT_SEQUENCE_EDITOR="$PWD/bin/git-cola-sequence-editor" \
git rebase -i origin/main

COMMAND-LINE TOOLS

The git-cola command exposes various sub-commands that allow you to quickly launch tools that are available from within the git-cola interface. For example, ./bin/git-cola find launches the file finder, and ./bin/git-cola grep launches the grep tool.

See git cola --help-commands for the full list of commands.

$ git cola --help-commands
usage: git-cola [-h]

                {cola,am,archive,branch,browse,config,
                 dag,diff,fetch,find,grep,merge,pull,push,
                 rebase,remote,search,stash,tag,version}
                ...

valid commands:
  {cola,am,archive,branch,browse,config,
   dag,diff,fetch,find,grep,merge,pull,push,
   rebase,remote,search,stash,tag,version}

    cola                start git-cola
    am                  apply patches using "git am"
    archive             save an archive
    branch              create a branch
    browse              browse repository
    config              edit configuration
    dag                 start git-dag
    diff                view diffs
    fetch               fetch remotes
    find                find files
    grep                grep source
    merge               merge branches
    pull                pull remote branches
    push                push remote branches
    rebase              interactive rebase
    remote              edit remotes
    search              search commits
    stash               stash and unstash changes
    tag                 create tags
    version             print the version

HACKING

The following commands should be run during development:

# Run the unit tests
$ make test

# Run tests and longer-running pylint and flake8 checks
$ make check

# Run tests against multiple python interpreters using tox
$ make tox

The test suite can be found in the test directory.

The tests are set up to run automatically when code is pushed using Travis CI. Checkout the Travis config file for more details.

Auto-format po/*.po files before committing when updating translations:

$ make po

When submitting patches, consult the contributing guidelines.

SOURCE INSTALL

For Linux/Unix-like environments with symlinks, an easy way to use the latest git cola is to keep a clone of the repository and symlink it into your ~/bin directory. If $HOME/bin is not already in your $PATH you can add these two lines to the bottom of your ~/.bashrc to make the linked tools available.

    PATH="$HOME/bin":"$PATH"
    export PATH

Then, install git-cola by linking it into your ~/bin:

    mkdir -p ~/src ~/bin
    git clone git://github.com/git-cola/git-cola.git ~/src/git-cola
    (cd ~/bin &&
     ln -s ../src/git-cola/bin/git-cola &&
     ln -s ../src/git-cola/bin/git-dag)

You should then get the latest git cola in your shell.

PACKAGING NOTES

Git Cola installs its modules into the default Python site-packages directory (eg. lib/python2.7/site-packages), and in its own private share/git-cola/lib area by default. The private modules are redundant and not needed when cola's modules have been installed into the site-packages directory.

Git Cola will prefer its private modules when the share/git-cola/lib directory exists, but they are not required to exist. This directory is optional, and can be safely removed if the cola modules have been installed into site-pacakges and are importable through the default sys.path.

To suppress the installation of the private (redundant) share/git-cola/lib/cola package, specify make NO_PRIVATE_LIBS=1 ... when invoking make, or export GIT_COLA_NO_PRIVATE_LIBS=1 into the build enviornment.

make NO_PRIVATE_LIBS=1 ...

Git Cola installs a vendored copy of its QtPy dependency by default. Git Cola provides a copy of the qtpy module in its private modules area when installing Git Cola so that you are not required to install QtPy separately. If you'd like to provide your own qtpy module, for example from the python-qtpy Debian package, then specify make NO_VENDOR_LIBS=1 ... when invoking make, or export GIT_COLA_NO_VENDOR_LIBS=1 into the build environment.

make NO_VENDOR_LIBS=1 ...

Python3 users on debian will need to install python3-distutils in order to run the Makefile's installation steps. distutils is a Python build requirement, but not needed at runtime.

WINDOWS (continued)

Development

In order to develop Git Cola on Windows you will need to install Python3 and pip. Install PyQt5 using pip install PyQt5 to make the PyQt5 bindings available to Python.

Once these are installed you can use python.exe to run directly from the source tree. For example, from a Git Bash terminal:

/c/Python36/python.exe ./bin/git-cola

Multiple Python versions

If you have multiple versions of Python installed, the contrib/win32/cola launcher script might choose the newer version instead of the python that has PyQt installed. In order to resolve this, you can set the cola.pythonlocation git configuration variable to tell cola where to find python. For example:

git config --global cola.pythonlocation /c/Python36

BUILDING WINDOWS INSTALLERS

Windows installers are built using

To build the installer using Pynsist run:

./contrib/win32/run-pynsist.sh

This will generate an installer in build/nsis/.

WINDOWS HISTORY BROWSER CONFIGURATION UPGRADE

You may need to configure your history browser if you are upgrading from an older version of Git Cola.

gitk was originally the default history browser, but gitk cannot be launched as-is on Windows because gitk is a shell script.

If you are configured to use gitk, then change your configuration to go through Git's sh.exe on Windows. Similarly, we must go through python.exe if we want to use git-dag.

If you want to use gitk as your history browser open the Preferences screen and change the history browser command to:

"C:/Program Files/Git/bin/sh.exe" --login -i C:/Git/bin/gitk

git-dag became the default history browser on Windows in v2.3, so new users should not need to configure anything.

Comments
  • Git Cola hangs during push process

    Git Cola hangs during push process

    _003 The push is successful but Git Cola hangs in this state. This issue is currently not always reproducible.

    Reporter's environment

    OS

    Ubuntu 14.04 x86 32bit

    Desktop environment

    KDE

    Python

    2.7.5

    Git

    1.9.1

    Locale

    zh_TW.UTF-8

    remote type

    HTTPS

    opened by Vdragon 44
  • User Config Not Recognized

    User Config Not Recognized

    The global user.name and user.email override the local config for me, regardless of if I specify the local config directly from git or through git-cola.

    This means that I often commit something with the incorrect Signed-off-by line.

    opened by skeggse 30
  • No GUI elements in Actions Window

    No GUI elements in Actions Window

    At some point git-cola stopped showing buttons in actions window. Now it's just empty dockable/resizable window. Already tried reinstalling.

    git: 1.7.2.1 git-cola: 1.4.2.2 py-qt: 4.7.4 python: 2.6.5 qt: 4.6.3 ArchLinux

    waiting pyqt bug 
    opened by alyst 30
  • Windows packaging using Pynsist

    Windows packaging using Pynsist

    This is still very rough. In particular, it should be smarter about finding the git executable - it currently assumes that it's installed in Program Files (the default location). I expect that arguments in general could be handled better - I just mocked out an args object quickly to get it running.

    Here is a sample installer built using current master, which works on my Windows 7 VM: https://www.dropbox.com/s/pxo0urszizgdhcx/Git_Cola_2.1.2.exe?dl=1

    To build:

    1. Download PyQt4 (http://sourceforge.net/projects/pyqt/files/PyQt4/PyQt-4.11.3/PyQt4-4.11.3-gpl-Py3.4-Qt4.8.6-x32.exe ) and unpack files from Lib/site-packages into pynsist_pkgs/ in the root of the git-cola repo. Then add files from $_OUTDIR/ into pynsist_pkgs/PyQt4. I hope to automate this step soon.
    2. rm share/doc/git-cola/html - this is a symlink, and copying it into the build directory currently fails.
    3. With pynsist and nsis installed, run pynsist windows-installer.cfg. The installer will be produced in build/nsis/
    opened by takluyver 27
  • git-dag hangs indefinitely on start

    git-dag hangs indefinitely on start

    Hello.

    I have git-cola @ 9c5473babfcb2e170f4d0c6dcce53abdb24a19a5. git-dag never launches whatever I do.

    Steps to reproduce (any of the following):

    • Run git-dag from a terminal inside git repository.
    • Run git-dag from a terminal outside git repository and choose one in the repo select dialogue.
    • From a running git-cola window click View->DAG.

    Expected results: git-dag is started.

    Actual results: Nothing happens. There are no errors or crashes. When started from a terminal git-dag just silently sits there indefinitely. Removing git-cola configuration from ~/.config doesn't help either.

    bug 
    opened by Coacher 25
  • pywin32 notify during build makes dag refresh all the time

    pywin32 notify during build makes dag refresh all the time

    With pywin32 for notify support, make -j4 makes the git dag blink all the time. dag feels the need to refresh commit list on changes to gitignored build directory.

    opened by sthalik 20
  • Git cola not saving configuration on Windows

    Git cola not saving configuration on Windows

    Whenever I edit Settings in preferences window ("Insert spaces instead of tabs", "Editor" etc.) the values are not saved. Closing the Preferences dialog and re-opening it shows the old (default) values.

    My system is Windows 10. I installed git-cola using the provided installer.

    Home directory settings (enforced by company IT):

    HOMEDRIVE=U:
    HOMEPATH=\
    

    Git cola version is 3.3.

    help wanted windows bug portability good first issue needs-user-testing 
    opened by mmoderau 19
  • TypeError: coercing to Unicode: need string or buffer, NoneType found

    TypeError: coercing to Unicode: need string or buffer, NoneType found

    I just installed git-cola from source in Ubuntu 16.04, and I'm getting this error upon launching:

    Traceback (most recent call last):
    
      File "/usr/share/git-cola/lib/cola/cmds.py", line 1915, in do_cmd
        return cmd.do()
    
      File "/usr/share/git-cola/lib/cola/cmds.py", line 1314, in do
        self.model.update_status(update_index=True)
    
      File "/usr/share/git-cola/lib/cola/models/main.py", line 194, in update_status
        self._update_merge_rebase_status()
    
      File "/usr/share/git-cola/lib/cola/models/main.py", line 246, in _update_merge_rebase_status
        self.is_merging = core.exists(self.git.git_path('MERGE_HEAD'))
    
      File "/usr/share/git-cola/lib/cola/core.py", line 294, in wrapped
        return decorator(fn(action(*args, **kwargs)))
    
      File "/usr/lib/python2.7/genericpath.py", line 26, in exists
        os.stat(path)
    
    TypeError: coercing to Unicode: need string or buffer, NoneType found
    
    

    I can't get past the error dialog, as soon as I click Close, a new one pops up. image

    bug 
    opened by dpashkevich 19
  • [Feature Request] PPA for Ubuntu based distros

    [Feature Request] PPA for Ubuntu based distros

    May you please create an official PPA for Ubuntu based distros because building from source whenever you created a new release is very frustrating procedure.

    PS.

    • Ubuntu repositories always have old version of git-cola
    • I found this PPA which is somehow older than recent release (2.1.2)
    help wanted packaging good first issue 
    opened by mbnoimi 19
  • macos, qtpy.PythonQtError: No Qt bindings could be found

    macos, qtpy.PythonQtError: No Qt bindings could be found

    Hi, brew upgraded my git cola and it stopped working :( please help My python version is Python 2.7.13 I see

    Traceback (most recent call last):
      File "/usr/local/Cellar/git-cola/2.9.1_1/share/git-cola/lib/qtpy/__init__.py", line 119, in <module>
        from PySide import __version__ as PYSIDE_VERSION  # analysis:ignore
    ModuleNotFoundError: No module named 'PySide'
    
    During handling of the above exception, another exception occurred:
    
    Traceback (most recent call last):
      File "/usr/local/bin/git-cola", line 54, in <module>
        from cola.main import main
      File "/usr/local/Cellar/git-cola/2.9.1_1/share/git-cola/lib/cola/main.py", line 9, in <module>
        from .app import add_common_arguments
      File "/usr/local/Cellar/git-cola/2.9.1_1/share/git-cola/lib/cola/app.py", line 14, in <module>
        from qtpy import QtCore
      File "/usr/local/Cellar/git-cola/2.9.1_1/share/git-cola/lib/qtpy/__init__.py", line 125, in <module>
        raise PythonQtError('No Qt bindings could be found')
    qtpy.PythonQtError: No Qt bindings could be found
    
    opened by johnykov 18
  • Bug on build for Arch Linux

    Bug on build for Arch Linux

    Command: yaourt -S git-cola

    Summary: erro: falha em submeter a transação (arquivos conflitantes)

    More info:

    :: Continuar a instalação? [S/n] s
    (19/19) verificando chaves no chaveiro                                      [###########################################] 100%
    (19/19) verificando integridade do pacote                                   [###########################################] 100%
    (19/19) carregando arquivos do pacote                                       [###########################################] 100%
    (19/19) verificando conflitos de arquivo                                    [###########################################] 100%
    erro: falha em submeter a transação (arquivos conflitantes)
    python-markupsafe: /usr/lib/python3.4/site-packages/MarkupSafe-0.23-py3.4.egg-info/PKG-INFO existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/MarkupSafe-0.23-py3.4.egg-info/SOURCES.txt existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/MarkupSafe-0.23-py3.4.egg-info/dependency_links.txt existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/MarkupSafe-0.23-py3.4.egg-info/not-zip-safe existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/MarkupSafe-0.23-py3.4.egg-info/top_level.txt existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/markupsafe/__init__.py existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/markupsafe/__pycache__/__init__.cpython-34.pyc existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/markupsafe/__pycache__/_compat.cpython-34.pyc existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/markupsafe/__pycache__/_constants.cpython-34.pyc existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/markupsafe/__pycache__/_native.cpython-34.pyc existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/markupsafe/__pycache__/tests.cpython-34.pyc existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/markupsafe/_compat.py existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/markupsafe/_constants.py existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/markupsafe/_native.py existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/markupsafe/_speedups.c existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/markupsafe/_speedups.cpython-34m.so existe no sistema de arquivos
    python-markupsafe: /usr/lib/python3.4/site-packages/markupsafe/tests.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__init__.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/__init__.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/_compat.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/_stringdefs.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/bccache.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/compiler.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/constants.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/debug.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/defaults.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/environment.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/exceptions.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/ext.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/filters.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/lexer.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/loaders.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/meta.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/nodes.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/optimizer.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/parser.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/runtime.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/sandbox.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/tests.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/utils.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/__pycache__/visitor.cpython-34.pyc existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/_compat.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/_stringdefs.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/bccache.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/compiler.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/constants.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/debug.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/defaults.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/environment.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/exceptions.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/ext.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/filters.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/lexer.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/loaders.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/meta.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/nodes.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/optimizer.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/parser.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/runtime.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/sandbox.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/tests.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/utils.py existe no sistema de arquivos
    python-jinja: /usr/lib/python3.4/site-packages/jinja2/visitor.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__init__.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__pycache__/__init__.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__pycache__/cmdline.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__pycache__/console.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__pycache__/filter.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__pycache__/formatter.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__pycache__/lexer.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__pycache__/modeline.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__pycache__/plugin.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__pycache__/regexopt.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__pycache__/scanner.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__pycache__/sphinxext.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__pycache__/style.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__pycache__/token.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__pycache__/unistring.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/__pycache__/util.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/cmdline.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/console.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/filter.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/filters/__init__.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/filters/__pycache__/__init__.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatter.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/__init__.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/__pycache__/__init__.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/__pycache__/_mapping.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/__pycache__/bbcode.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/__pycache__/html.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/__pycache__/img.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/__pycache__/latex.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/__pycache__/other.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/__pycache__/rtf.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/__pycache__/svg.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/__pycache__/terminal.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/__pycache__/terminal256.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/_mapping.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/bbcode.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/html.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/img.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/latex.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/other.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/rtf.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/svg.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/terminal.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/formatters/terminal256.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexer.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__init__.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/__init__.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/_asy_builtins.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/_cl_builtins.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/_cocoa_builtins.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/_lasso_builtins.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/_lua_builtins.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/_mapping.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/_mql_builtins.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/_openedge_builtins.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/_php_builtins.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/_postgres_builtins.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/_scilab_builtins.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/_sourcemod_builtins.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/_stan_builtins.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/_vim_builtins.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/actionscript.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/agile.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/algebra.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/ambient.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/apl.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/asm.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/automation.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/basic.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/business.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/c_cpp.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/c_like.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/chapel.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/compiled.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/configs.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/console.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/css.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/d.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/dalvik.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/data.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/diff.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/dotnet.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/dsls.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/dylan.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/ecl.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/eiffel.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/erlang.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/esoteric.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/factor.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/fantom.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/felix.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/fortran.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/foxpro.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/functional.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/go.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/graph.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/graphics.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/haskell.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/haxe.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/hdl.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/html.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/idl.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/igor.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/inferno.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/installers.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/int_fiction.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/iolang.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/javascript.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/julia.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/jvm.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/lisp.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/make.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/markup.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/math.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/matlab.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/ml.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/modeling.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/nimrod.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/nit.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/nix.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/objective.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/ooc.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/other.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/parsers.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/pascal.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/pawn.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/perl.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/php.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/prolog.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/python.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/r.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/rdf.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/rebol.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/resource.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/robotframework.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/ruby.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/rust.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/scripting.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/shell.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/smalltalk.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/snobol.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/special.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/sql.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/tcl.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/templates.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/testing.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/text.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/textedit.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/textfmts.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/theorem.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/urbi.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/web.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/__pycache__/webmisc.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/_asy_builtins.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/_cl_builtins.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/_cocoa_builtins.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/_lasso_builtins.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/_lua_builtins.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/_mapping.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/_mql_builtins.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/_openedge_builtins.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/_php_builtins.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/_postgres_builtins.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/_scilab_builtins.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/_sourcemod_builtins.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/_stan_builtins.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/_vim_builtins.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/actionscript.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/agile.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/algebra.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/ambient.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/apl.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/asm.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/automation.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/basic.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/business.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/c_cpp.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/c_like.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/chapel.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/compiled.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/configs.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/console.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/css.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/d.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/dalvik.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/data.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/diff.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/dotnet.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/dsls.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/dylan.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/ecl.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/eiffel.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/erlang.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/esoteric.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/factor.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/fantom.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/felix.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/fortran.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/foxpro.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/functional.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/go.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/graph.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/graphics.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/haskell.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/haxe.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/hdl.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/html.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/idl.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/igor.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/inferno.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/installers.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/int_fiction.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/iolang.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/javascript.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/julia.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/jvm.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/lisp.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/make.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/markup.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/math.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/matlab.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/ml.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/modeling.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/nimrod.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/nit.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/nix.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/objective.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/ooc.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/other.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/parsers.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/pascal.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/pawn.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/perl.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/php.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/prolog.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/python.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/r.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/rdf.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/rebol.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/resource.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/robotframework.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/ruby.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/rust.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/scripting.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/shell.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/smalltalk.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/snobol.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/special.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/sql.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/tcl.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/templates.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/testing.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/text.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/textedit.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/textfmts.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/theorem.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/urbi.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/web.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/lexers/webmisc.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/modeline.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/plugin.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/regexopt.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/scanner.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/sphinxext.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/style.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__init__.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/__init__.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/autumn.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/borland.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/bw.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/colorful.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/default.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/emacs.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/friendly.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/fruity.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/igor.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/manni.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/monokai.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/murphy.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/native.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/paraiso_dark.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/paraiso_light.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/pastie.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/perldoc.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/rrt.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/tango.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/trac.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/vim.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/vs.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/__pycache__/xcode.cpython-34.pyc existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/autumn.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/borland.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/bw.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/colorful.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/default.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/emacs.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/friendly.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/fruity.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/igor.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/manni.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/monokai.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/murphy.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/native.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/paraiso_dark.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/paraiso_light.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/pastie.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/perldoc.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/rrt.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/tango.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/trac.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/vim.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/vs.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/styles/xcode.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/token.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/unistring.py existe no sistema de arquivos
    python-pygments: /usr/lib/python3.4/site-packages/pygments/util.py existe no sistema de arquivos
    python-six: /usr/lib/python3.4/site-packages/__pycache__/six.cpython-34.pyc existe no sistema de arquivos
    python-six: /usr/lib/python3.4/site-packages/six.py existe no sistema de arquivos
    Ocorreram erros e, portanto, nenhum pacote foi atualizado.
    ==> Reiniciar a compilação de git-cola ? [s/N]
    
    not-a-bug 
    opened by alexandre-mbm 18
  • Add context menu in prompt dialog (git cola --prompt)

    Add context menu in prompt dialog (git cola --prompt)

    According to this issue, "Cannot remove old folders from git-cola main window #1199", I implemented context menu in prompt dialog (git cola --prompt).

    The content of the context menu is same as favorite(and recent) widget (in cola/widgets/bookmarks.py) in main UI. A lot of context menu functions come from the code.

    • Open
    • Open in New WIndow
    • Open Using Default Application
    • Copy
    • Launch Editor
    • Launch Terminal
    • Clear Deafult Repository
    • Rename Repository
      • only activated in "Folder" tab [1]
    • Delete from Bookmakrs List
      • only in Favorites view
    • Delete from Recent List
      • only in Recent view
    • Prune Missing Entries

    NOTE

    [1] In "List" tab, each item text is its repository's full path like /home/foo/some-repository. So, in "List" tab, set all items UNEDITABLE.

    prompt-capture

    Fixes #1199 Thank you!

    opened by nakanoi 9
  • git-bindir is being ignored on Windows

    git-bindir is being ignored on Windows

    Since I currently have the misfortune of having to use Windows (and at that one without admin rights) I installed both Git and Git-Cola there. Unfortunately Git doesn't stay on the path, so as advised in the error dialog box, I tried creating the git-bindir file with the following content:

    C:\Users\ziltenerd\AppData\Local\Programs\Git\bin
    

    I created it both at the C:\Users\ziltenerd\.config\git-cola directory that gets auto-created as well as at C:\Users\ziltenerd\AppData\Roaming\.config\git-cola. Both had no effect at all.

    opened by zilti 7
  • Feature Request: Open multiple repos with tabbed interface

    Feature Request: Open multiple repos with tabbed interface

    Hello git-cola team,

    I think it would be really nice if you could open multiple repositories at once within a single instance of the app and be able to navigate between them using a tabbed interface (i.e. like web browser tabs).

    This is useful when you're working on something that spans across several related repos, or when you want to leave open your most frequently used repos for when you next start the app.

    Cheers.

    usability enhancement 
    opened by craigwardman 1
  • App version broken in macOS Monterrey

    App version broken in macOS Monterrey

    What works

    1. ./git-cola.app/Contents/MacOS/git-cola from Terminal (Terminal has Full Disk Access)
    2. git-cola (from Terminal, installed by brew, Terminal has Full Disk Access)

    What doesn't work

    1. open git-cola.app
    2. Double clicking git-cola.app from within Finder or Launchpad

    What happens

    The GUI to select which repository opens fine. But after trying to open a repository, the app will just close with no feedback (likely a crash)

    Diagnostic

    It appears to be a permission problem:

    A

    All those System Policy: ... deny ... file-read-data appear right after I double click the repository to open in git-cola and crashes /Users/matias/Documents/git-cola is the repository I'm trying to open.

    Adding git-cola.app and /usr/bin/git to Full Disk Access doesn't fix it:

    Untitled

    macos 
    opened by darksylinc 1
  • Custom GIT_DIR is not respected when starting git-cola

    Custom GIT_DIR is not respected when starting git-cola

    Steps to reproduce:

    # run in blank dir
    
    export GIT_DIR=.gitgit
    export GIT_WORK_TREE=.
    
    # create empty repo
    git init
    
    ls
    # => should show .gitgit
    
    git status
    # => should not error, git respects these variables
    
    git-cola
    # doesn't recognize the repo  in current dir, shows repo chooser dialog instead
    

    This kind of breaks git-cola for custom .git dirs, although all the machinery is there (in git.py).

    opened by sergei-dyshel 2
Releases(v4.1.0)
git-cola: The highly caffeinated Git GUI

git-cola: The highly caffeinated Git GUI git-cola is a powerful Git GUI with a slick and intuitive user interface. Copyright (C) 2007-2020, David Agu

git-cola 2k Dec 30, 2022
Trac is an enhanced wiki and issue tracking system for software development projects (mirror)

About Trac Trac is a minimalistic web-based software project management and bug/issue tracking system. It provides an interface to the Git and Subvers

Edgewall Software 442 Dec 10, 2022
The new home of rabbitvcs

RabbitVCS RabbitVCS is a set of graphical tools written to provide simple and straightforward access to the version control systems you use. We curren

RabbitVCS 349 Dec 05, 2022
Mirror of Apache Allura

Apache Allura Allura is an open source implementation of a software "forge", a web site that manages source code repositories, bug reports, discussion

The Apache Software Foundation 106 Dec 21, 2022
Patchwork is a web-based patch tracking system designed to facilitate the contribution and management of contributions to an open-source project.

Patchwork Patchwork is a patch tracking system for community-based projects. It is intended to make the patch management process easier for both the p

Patchwork 220 Nov 29, 2022
A simple version control system built on top of Git

Gitless Gitless is a version control system built on top of Git, that is easy to learn and use: Simple commit workflow Track or untrack files to contr

Gitless 1.7k Dec 22, 2022
docker run klaus / pip install klaus — the first Git web viewer that Just Works™.

klaus: a simple, easy-to-set-up Git web viewer that Just Works™. (If it doesn't Just Work for you, please file a bug.) Super easy to set up -- no conf

Jonas Haag 638 Dec 24, 2022
🦉Data Version Control | Git for Data & Models

Website • Docs • Blog • Twitter • Chat (Community & Support) • Tutorial • Mailing List Data Version Control or DVC is an open-source tool for data sci

Iterative 10.9k Jan 09, 2023
ViewVC is a browser interface for CVS and Subversion version control repositories.

ViewVC - Version Control Browser Interface ViewVC is a browser interface for CVS and Subversion version control repositories. It generates templatized

ViewVC 270 Dec 30, 2022