[root@tower2 firewall]# pacman -Sq monotone
error: target not found: monotone
[root@tower2 firewall]# pacman -Syu monotone
:: Synchronizing package databases...
core121.7 KiB 231K/s 00:01
[] 100%
extra
Arch Linux *does* have a package for monotone:
https://aur4.archlinux.org/packages/monotone/
It builds against botan stable.
Simply issue:
yaourt -Syua monotone
or
git clone https://aur.archlinux.org/monotone.git
cd monotone && makepkg -s
J Decker:
> Arch Linux has no package for monotone.
On 03/03/2016 03:37 AM, J Decker wrote:
> Arch Linux has no package for monotone.
> it installs a Botan-1.11(?) as 'Botan'
You reported this before and were told that Botan 1.11 is a development
branch. Please compile Monotone against 1.10, instead. (Or 1.6 or 1.8,
if you insist.)
Plus:
Thomas Keller schrieb:
William Uther schrieb:
Hi all,
I notice that the current head fails to build the documentation on
MacOS X if you're using the fink package manager for your dependencies.
The problem is that the fink package manager has an ancient version of
gettext (0.14) and its
On Wed, Mar 4, 2009 at 8:43 AM, Zack Weinberg za...@panix.com wrote:
On Wed, Mar 4, 2009 at 4:13 AM, Thomas Keller m...@thomaskeller.
...the question is if we really need these options for anything else than
commentary in the pot header...
We don't really. I can do something about this later
William Uther schrieb:
Hi all,
I notice that the current head fails to build the documentation on
MacOS X if you're using the fink package manager for your dependencies.
The problem is that the fink package manager has an ancient version of
gettext (0.14) and its version of xgettext
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Joe!
I'm seeing a build failure of the 0.36 code.
I'm on a Gnu/Linux box, with an AMD64 architecture (dual core
opteron) running Kubuntu (dapper):
[...]
g++ -DLOCALEDIR=\/usr/local/monotone/monotone-0.36/share/locale\
-DHAVE_CONFIG_H
On Thu, 2008-01-03 at 14:36 +0100, Thomas Keller wrote:
Sorry that this took a little longer, but I recently stumbled across
the
same problem. The origin seems to be gcc, which did not provide
default
constructors for Internal::hastable_iterator and
Internal::hashtable_const_iterator [0].
