New release tarball apparently mis-named
by Rowan Thorpe
I noticed that the new 0.9.3 release download tarball, signature, etc have some
kind of naming problem where it has been numbered with a concatenation of 0.9.2
and 0.9.3 instead (e.g. coquelicot-0.9.30.9.2.tar.gz). Aside from the cosmetic
aspect, it will probably confuse maintainers' tools like uscan...
10 years, 8 months
[ANNOUNCE] Coquelicot 0.9.3
by Lunar
Hi!
Coquelicot 0.9.3 is out!
What's new?
===========
Nothing super fancy feature-wise, but “sub-directory” installation
support, Spanish translation and a new LDAP authentication method.
The rest is mostly about keeping pace with the Ruby ecosystem.
Coquelicot should now work fine with Ruby 1.9.1, 2.0 and 2.1.
In details:
* Support sub-directory installations. See updated installation
documentation for Apache and the new `path` setting.
* Always use the current source tree as the `coquelicot` gem.
* Fix an issue with the signature step in the release process.
* Document commands needed to serve the local Git clone.
* Fix a typo in footer when Coquelicot was installed from a gem.
* Add missing Debian packages to installation steps. Thanks Alexandre
Garreau for reporting the issue.
* Add Spanish translation. Thanks Loïc Raimbault!
* Stop spilling authentication errors to users. Thanks Rowan Thorpe for
the report.
* Add LDAP authentication (with uid lookup). Thanks Rowan Thorpe!
* Code cleanups:
- Drop support for Ruby 1.8.
- Stop using unsupported gem name for `activesupport`.
- Set a default time zone when running tests.
- Ensure same timezone when testing file creation time.
- Add support for generating gems using the newer Gem API.
- Add support for the Psych YAML engine.
- Switch to new RSpec expectation syntax.
- Switch to GetText::Tools:Task in Rakefile.
- Update bundle dependencies.
Upgrade procedure
=================
If you have installed Coquelicot from a source tarball, unpacking
the new tarball on top of the previous one should do the trick.
If you have installed Coquelicot using a clone of the Git repository,
the update should be as simple as:
git fetch origin
git tag -v coquelicot-0.9.3
git merge --ff-only coquelicot-0.9.3
Download
========
The source tarball can be downloaded at:
<https://coquelicot.potager.org/dist/coquelicot-0.9.3.tar.gz>
OpenPGP signature:
<https://coquelicot.potager.org/dist/coquelicot-0.9.3.tar.gz.asc>
SHA1 checksum: 23580deed2bd91e79cddecaf3eaf9f0ae99c586f
SHA256 checksum: 9ca7491c3f0b25000659e6bce5a35ec1283a0405b5dcb3333cfad0b4755d3ed1
--
Lunar
10 years, 8 months
LDAP authentication support
by Rowan Thorpe
I have just finished getting LDAP authentication working with Coquelicot
(modelled very closely on the existing IMAP code), and would love to share it
back to the project, but am not sure exactly where and how. I doubt I have
access to interact with the repo in any way other than cloning from it, and I
doubt you would want me to email a huge patch to the mailing list?
Should I upload my repo to github or somewhere public like that, for you to
pull from? Or can I send you a pull request somewhere?
--
Rowan Thorpe
mailto:rowan@rowanthorpe.com
10 years, 8 months
