Size: 5293
Comment: update for r1007
|
Size: 5354
Comment: debian builds get
|
Deletions are marked like this. | Additions are marked like this. |
Line 17: | Line 17: |
|| 2014-01-20 || [[http://code.bitlbee.org/lh/bitlbee/revision/1007|1007]] || -- || 4 ||<#AAFFAA> Yes ||<#AAFFAA> Yes || OTR fixes by pesco! Seems to work flawlessly. || bzr - '''no debian builds yet''' || | || 2014-01-20 || [[http://code.bitlbee.org/lh/bitlbee/revision/1007|1007]] || -- || 4 ||<#AAFFAA> Yes ||<#AAFFAA> Yes || OTR fixes by pesco! Seems to work flawlessly. || bzr, .deb repo (or APT), [[http://code.bitlbee.org/tarballs/bitlbee-bzr-1007.tar.gz|.tar.gz]] || |
Version reference tables
BitlBee
Since the switch to libotr4 overlapped with the fixes for twitter (which is the main reason 3.2.1 was released), and additionally debian released their own version with a name that's suspiciously similar to 3.2.1, here's a table that documents all the relevant versions to both OTR and Twitter support.
Date |
bzr |
Release |
libotr |
Twitter? |
Stable? |
Notes |
Where to get |
2013-01-06 |
3.2 1 |
3 |
No |
Yes |
The original 3.2 release. Old but stable. |
bzr, Release .tar.gz |
|
2013-06-16 |
-- |
3 |
Yes |
Yes |
Earliest dev build with most twitter fixes |
bzr |
|
2013-07-13 |
-- |
3 |
Yes |
Yes |
Latest dev build with libotr3 support available from the APT repo |
bzr, .deb repo, .tar.gz |
|
2013-10-14 |
-- |
3 |
Yes |
Yes |
Minor bug fix that doesn't have any .deb builds in the repo |
bzr, .tar.gz |
|
2013-11-27 |
3.2.12 |
3 |
Yes |
Yes |
Official 3.2.1 release |
bzr, Release .tar.gz |
|
2013-12-05 |
-- |
3 |
Yes |
Yes |
Minor fix for the displayed version |
bzr |
|
2013-12-05 |
-- |
4 |
Yes |
No |
bzr, .deb repo, .tar.gz |
||
2013-12-19 |
3.2.1+otr4-1 |
4 |
Yes |
No |
Release for debian jessie/sid and ubuntu trusty only. |
bzr, .deb repo, debian/ubuntu |
|
2014-01-20 |
-- |
4 |
Yes |
No |
Fix attempt, unsuccessful. |
bzr, .deb repo, .tar.gz |
|
2014-01-20 |
-- |
4 |
Yes |
Yes |
OTR fixes by pesco! Seems to work flawlessly. |
bzr, .deb repo (or APT), .tar.gz |
The bzr builds before the 3.2.1 release show their version number in the format 3.2+20130714+devel+997-1. In the case of bzr997, it has almost all the features of the 3.2.1 release (except the bugfix from 998), so the "3.2" part of the version number might be misleading, but what matters is the "997" part.
"What should I use?"
Installation method |
Twitter needed? |
OTR needed? |
Min-max bzr |
Recommended version |
Notes |
.deb / APT |
Yes |
Yes |
991 - 997 or 1007 - * |
1007 / Latest build. |
The latest version in the apt repo is stable now |
.deb / APT |
Yes |
No |
991 - * |
1007 / Latest build. |
The OTR plugin can be kept if using builds >1007 |
.deb / APT |
No |
No |
965 - * |
1007 / Latest build. |
Same as above. Any version >=3.2 will also work. |
.deb / APT |
No |
Yes |
965 - 997 or 1007 - * |
1007 / Latest build. |
Any version >=3.2 will also work. |
Manual compilation |
Yes |
-- |
991 - 1000 or 1007 - * |
You can also try newer bzr revisions since 1007 to compile against libotr4 |
|
Manual compilation |
No |
-- |
965 - 1000 or 1007 - * |
No need to upgrade if you have a version >=3.2. |
OTR
And here's another table for the apparent nonsense of the OTR versions.
Library |
Protocol |
.so name (ABI version) |
Debian package |
Supported bitlbee releases |
Supported bitlbee bzr |
Stability |
libotr 3.2.1 |
libotr.so.2.2.1 |
libotr2(-dev) |
3.0 ... 3.2.1 |
<=1000 |
Stable |
|
libotr 4.0.0 |
libotr.so.5.0.0 |
libotr5(-dev) |
Debian's "3.2.1+otr4-1"* |
>=1001 |
Stable since r1007 |
The stability column refers to the current bitlbee support, which might crash in some situations. Bug