Pygit2 0.22.0 released, updates to libgit2 0.22.0

This release requires the recently released libgit2 0.22.0; other changes include an improved support for remotes. See the full list of changes.

Thanks to Carlos Martín Nieto, Matthew Duggan, Greg Fitzgerald, Kevin Kin-Foo, Richard Möhn, Lukas Fleischer, Peter Dave Hello and Philippe Ombredanne.

Resources:

Enjoy!

Pygit2 0.21.2 fixes regression, use it with libgit2 0.21.1

This release fixes a regression introduced in version 0.21.0, with the index and Python 2. See the full list of changes.

Thanks to Carlos Martín Nieto and Arno van Lumig.

Otherwise most important is the maintenance release of libgit2 v0.21.1, which among other corrections fixes a critical bug which may lead to data corruption. See the full list of libgit2 v021.1 changes.

So upgrading to libgit2 0.21.1 and pygit2 0.21.2 is highly recommended.

Resources:

Enjoy!

Pygit2 0.21.1 and a new skin for the documentation

Changes:

  • Documentation: use the read-the-docs theme
  • New Repository.state_cleanup()
  • New Index.conflicts
  • New checkout option to define the target directory
  • And more…

Thanks to Carlos Martín Nieto, Vlad Temian and Jasper Lievisse Adriaanse.

Release partially sponsored by Bors LTD

Resources:

Enjoy!

 

Pygit2 0.21.0 uses cffi

Changes:

  • Now using cffi
  • Upgraded to libgit2 latest and greatest v0.21.0
  • And much more…

Thanks to Carlos Martín Nieto, Michael Jones, Ian P. McCullough, Jack O’Connor, Thomas Kluyver, Daniel Bruce and Jun Omae.

Release partially sponsored by Bors LTD

Resources:

Enjoy!

pygit2 0.20.3 introduces support for credentials

Changes:

  • Introduce support for credentials
  • Several memory issues fixed
  • Compatibility fixes for Python 3.3, PyPy3 and Visual Studio
  • And much more…

Thanks to Carlos Martín Nieto, Leonardo Rhodes, Devaev Maxim, Erik Meusel, Thomas Kluyver and earl.

Resources:

Enjoy!

pygit2 version 0.20.2 adds support for pypy

Changes:

  • Support pypy
  • Much improved support for remotes
  • Improved support for index entries
  • A couple of leaks fixed
  • And much more…

Thanks to Carlos Martín Nieto, Xu Tao, Alexander Bayandin and Petr Hosek.

Resources:

Enjoy!

pygit2 version 0.20.1 brings support for merge and reset

Changes:

  • New remote ref-specs API: #290
  • New Repository.reset(...): #292, #294
  • Export GIT_DIFF_MINIMAL: #293
  • New Repository.merge(...): #295
  • Fix Repository.blame argument handling: #297
  • Fix build error on Windows: #298
  • Fix typo in the README file, Blog → Blob: #301
  • Now Diff.patch returns None if no patch: #232, #303
  • New Walker.simplify_first_parent(): #304

Thanks to Jose Plana, Victor Garcia, Petr Hosek, Adam Spiers, Eric Schrijver,  Óscar San José and Xu Tao.

Resources:

Enjoy!

pygit2 0.20.0 adds support for blame

New in this release is support for blame, and upgrade to libgit2 0.20. Detailed list of changes follows.

Changes:

  • Renamed Repository.head_is_orphaned to Repository.head_is_unborn
  • Repository.listall_references and Repository.listall_branches now return a list, instead of a tuple
  • The prototype of clone_repository changed
  • Added support for blame
  • New:
    • Reference.log_append(...)
    • Reference.shorthand
    • Blog.is_binary
    • len(Diff)
    • Patch.additions
    • Patch.deletions
    • Patch.is_binary

Thanks to:

  • Carlos Martín Nieto
  • Xu Tao
  • Huang Huang
  • Petr Hosek

Resources:

Enjoy!

pygit2 0.19.1 released

New in this release is support for push. Detailed list of changes follows.

API changes:

  • Rename Commit._message to Commit.raw_message
  • Rename Signature._name to Signature.raw_name
  • Rename Signature._email to Signature.raw_email

New features:

  • Remote.push(refspec)
  • Tag.get_object()

And some bugs fixed.

Thanks to:

  • Brodie Rao
  • Fraser Tweedale
  • Andrew Chin
  • Carlos Martín Nieto

Resources:

Enjoy!

Collectd Front-ends

Finally, I found a good enough Collectd front-end: the Collectd Graph Panel (CGP). But first lets look at those front-ends which did not pass the exam:

  • Collectd-web is the first I tried, maybe because it is the only one with a package in Gentoo (but it is poor package, so I ended up installing from source). My main complain is that some graphs, like the very useful context-switches, don’t work. It is also quite slow generating the graphs.
  • Collection4, developed by the lead developer of collectd, did not even build. I did not insist.

Many of the front-ends listed in the collectd wiki page were discarded either because they looked like dead (no new commit in the last few years) or because their deployment process was too cumbersome (need to setup database…). But I still tried a few more:

  • Sickmuse is sleek. However there are some details in the way to deployment, like there is no option to make server to listen only the local interface. Alright, it’s just Python, I can fix it… Problem is, the build process requires to install npm (the Node.js package manager), just to install another package manager named Bower, just to install the JS and CSS.
  • Jarmon is very simple to deploy but requires to define every plugin in the front-end, i.e. it is unable to discover the hosts and plugins just like every other front-end does. So it is a pain in the ass to maintain.
  • Visage just shows nothing. I tried to add a host and plugins through the web interface, but the interface is buggy.

Like when looking for the keys, the answer was in the last pocket. Well, the CGP web site is designed to discourage potential users. There is no documentation. I had to dig a little to find out how to get it working with Nginx for instance.

Just one note about CGP, it has two modes to generate the graphs: PNG (the default) and canvas, to generate the graphs in the browser. The canvas mode did not work for me: zooming with the mouse scroll is so sensible it is unusable; it is slow, the fan in my notebook started to run like crazy; my browser even gave me some error like “This scripts is stalled, kill it?”. But the PNG mode is fine.

Conclusion. The weakness of Collectd is the lack of a good and well established front-end. Instead there are more than a dozen front-ends of varying quality. This is my selection:

  1. CGP. Don’t look any further, unless you have some free time.
  2. Visage. This one is promising, maybe I will try again once they get 3.0 out.
  3. Sickmuse. If it only was less trendy and more practical… Three things to improve: the build process, deployment and usability.