Package Details: cjdns-git 20.2-1

Git Clone URL: (read-only)
Package Base: cjdns-git
Description: A routing engine designed for security, scalability, speed and ease of use
Upstream URL:
Licenses: GPL3
Conflicts: cjdns
Provides: cjdns
Submitter: prurigro
Maintainer: prurigro
Last Packager: prurigro
Votes: 39
Popularity: 0.873116
First Submitted: 2012-02-06 04:01
Last Updated: 2018-05-02 03:36

Dependencies (6)

Required by (3)

Sources (1)

Latest Comments

prurigro commented on 2014-05-19 07:22

Anyone who needs/wants to build crashey instead of master can edit the PKGBUILD before building and replace the "=master" in source to "=crashey" like so: source=("git://${_pkgname}.git#branch=crashey"). One day master might be more stable while crashey might be on another, and sometimes which depends on what your platform and usecase is.

gant commented on 2014-05-18 15:18

Any change of an alternative package for the crashy branch (which most of the time is actually more stable than master)

prurigro commented on 2014-02-24 02:41

@lgbsneak: Hey there- can I ask more details about your environment, configuration, board etc? I missed your message when you'd sent it so the issue might be a bit out of date by now, but my own armv7h wasn't giving me any issues when you sent your message either.


lgbsneak commented on 2014-01-04 04:12

Build fails on armv7h with crypto_sign/ed25519/ref10/fe.h:6:1: error: unknown type name ‘crypto_int32’

prurigro commented on 2013-12-31 15:14

The script and its config file were removed from the cjdns repo, so I've moved them to cjdns-git-sysvinit and taken references out of this package. I also cleaned things up a tiny bit and added some comments if that matters to anyone.


prurigro commented on 2013-12-27 19:46

Thanks kamiljk89, qmx and derp (via irc)-- I've pushed an update here that gets things working without the scripts, and I'll follow up re: scripting after I get back from a ski trip in Vermont for the weekend.

kamiljk87 commented on 2013-12-24 15:15

Build fail... near cjdroute2 cant find file...

qmx commented on 2013-12-24 01:56

last cjd's push broke everything mostly, the scripts vanished
I have a pull request sitting with the changes, but all my peers went the way of the dodo apparently so I'm waiting on getting connectivity again to be 100% sure it didn't break everything

prurigro commented on 2013-12-16 11:46

Package has been updated: removed the cjdns binary as it's built into cjdroute, and cmake is now a makedep (I thought I'd added that previously but I guess not?)

prurigro commented on 2013-09-17 02:42

Updated to remove cjdns.install, which ran the command "systemctl --system daemon-reload" on systems with systemd when the package was updated so that systemd wouldn't complain when using systemctl. This turned out to be bad practice, and could have potentially caused issues since all services get reloaded when this is run, so you'll need to run it on your own if you want to skip the warning after a reinstall.

prurigro commented on 2013-09-16 18:54

Updated to remove the pointless python->python2 find/replace in prepare()

prurigro commented on 2013-09-16 06:00

New version of the package! Updates include:
- Contrib scripts (the ones that mostly require python2) are no longer included in this package, and to take their place I've created a new package called 'cjdscript' (included in the optional deps) that provides a utility to install and run those scripts from a local installation it maintains.
- The /etc/default/cjdns configuration file, used by for control over a non-system (systemd) cjdns process, is now included in this package rather than the cjdns-git-sysvinit one.

@elasticdog: I came up with a solution for providing scripts without including them in this package, let me know what you think if you give it a shot (cjdscript package, or if don't necessarily want it installed at the system level.)

As far as the cmake issue is concerned; the final decision not to use it as a makedep was based on the responses I got when I asked a bunch of the folks on IRC who use the package. I do hear you in respect to not having the PKGBUILD pulling in its own deps though, and I don't consider the debate over (I've just been focusing more on your initial suggestion to remove the scripts untill now.) Fauno filled me in on the logic behind not having installation scripts pull in anything external, and I do agree, though I want to run things by others on the network to make sure there are no excellent arguments in other directions. In respect to libnacl, the cjdns package already includes a compressed file containing libnacl when you run 'git pull', so it's not quite the same situation either.

I will follow up in any case. If anyone else has comments on the above discussion, please share them! :)

elasticdog commented on 2013-08-28 20:18

FYI, it looks like the libnacl check wasn't working before [1] (aside from on OpenWrt). I do see where you're coming from regarding the space on your particular machine, but that seems like an edge case...python2 alone is twice the size of cmake. I'd assume that people running on similar platforms would know enough to provide their own workarounds for the space constraints.

Anyway, it's mostly a philosophical debate at this point with me preferring to let the package manager explicitly handle dependencies rather than the build process. I could understand leaving libnacl as an optdepends, as it's only available in the AUR, so leaving it optional lowers the barrier to entry.

Either way, I'm fine maintaining my own PKGBUILD, but was just offering suggestions on how it would be easiest for the widest audience (I was a TU for 4 years).


prurigro commented on 2013-08-23 07:43

@elasticdog: Hrm, libnacl worked for me last time I tried it, you should give it another shot. The space argument is simple; I have room in my /tmp ramdisk to build cmake but not on my disk to install it, and since cjdns compiles properly both ways, why not allow people to choose whether or not they want to speed up the compile based on their system? In respect to the python2 issue; I've been giving it some thought and agree with you now that makepkg complains about missing deps when the requirements for a script are missing. I plan to see if I can get a package made without pulling the entire sources, and then there's maintenance to consider too... Something will come of this issue in the near future anyway. As far as cherry picking goes though; I've added every utility that I tested successfully, and the ones I didn't were either examples or non-working in one way or another, so it wasn't completely at random.

elasticdog commented on 2013-08-23 06:30

I'm not understanding the space argument. Having cmake as a makedepends ensures that the package is installed, which is the already-compiled binary and should take up less space than having the ./do script download the cmake source and compile those same binaries. Plus, it can be removed after building the package if you don't want it taking up space on your system.

Admittedly, I never got the ./do script to properly utilize libnacl when it was installed, but that was a while ago, so perhaps I should try again and take a look at the actual logic in the build script.

I still think the python2 utilities should be split out...yes the code is technically in the cjdns repo, but the contrib files are explicitly "not officially part of cjdns but [are] useful as a complement". It just seems like arbitrary cherry picking of certain utilities and ignoring all of the others...none of which are required. Personally, I prefer using cjdcmd and none of the tools from contrib.

fauno commented on 2013-08-21 13:19

I've uploaded a modified version of your PKGBUILD to Parabola's repos. This version builds correctly on a clean chroot. I added python2 and cmake to the makedepends array and didn't remove the CFLAGS, there's a bundled lib that complains about building without optimizations but the rest is ok. Thanks!

prurigro commented on 2013-08-21 07:10

The package has been updated!

Changes include moving sysvinit support into a separate package and adding numerous optional dependencies.

@elasticdog: The problem with adding cmake to the makedepends is that people are then required to have cmake installed, which some systems don't have the space for (my tinykvm node for example) In respect to nacl; cnacl is simply upstream nacl with a cmake build script written by cjd, so if you have the upstream nacl installed (provided by the libnacl package in the AUR), you can skip the cnacl build step too. Neither of these packages are required, but they're both useful if you can afford the space to install them, and you've raised a good point about people not being aware that they can speed things up by having them, so I've thrown them into the optional dependencies array with explanations :)

As for sysvinit support; despite deprecation (I actually believe it's been made obsolete if I'm not mistaken), people using Arch as a chroot environment (which is done as one of the methods for running cjdns on an Android phone, for example) don't have systemd running in the background, and having an init script is useful. Now that said, you've made me realize that it's a pretty fringe case at this point, and I've opted to move support into a different package which I've added to the optional dependencies array as well.

The pythons junk is a bit different since those scripts come from within the cjdns repo itself, and therefore moving support into another package would mean having everyone who wants them installed to download cjdns twice each update... If split packages were compatible with the AUR I'd switch cjdns-git over in a heartbeat (you might notice that the PKGBUILD is already configured to make the transition), but in the meantime, if you don't want support for those scripts you can simply comment out the line in the package() function that calls the function that adds them.

elasticdog commented on 2013-08-20 20:46

My $0.02 would be to have the package include cmake for the makedepends so you can utilize the regular Arch package and bypass downloading it via the ./do install script. I'd hope that long-term, the ./do install script would get away from downloading and installing any dependencies and just let the package manager deal with them. Perhaps a package for 'cnacl' should be made.

Anyway, I'd also suggest dropping the sysvinit stuff altogether as it has been deprecated since November of last year and the final official warning about its removal went out over six months ago. You could then split out the other utilities into their own 'cjdns-contrib-python' or whatever package so people wouldn't have to do any manual editing of the PKGBUILD.

prurigro commented on 2013-08-20 20:18

@fauno: Ahoy there! The build should work without cmake, does it not for you? Also, python2 is an optional dep to support certain scripts, and it was done like this on purpose after some debate (though the debate is still open), but is there a point in the actual build process that requires python2-config, or is script support what you were referring to? I just ran some tests and wasn't able to find it if there is... Cheers!

fauno commented on 2013-08-20 19:40

it needs cmake on makedepends :)

(it also wants "python2-config" but it continues without it)

prurigro commented on 2013-08-09 06:58

Package Update: PKGBUILD now unsets $MAKEFLAGS to avoid issues like elasticdog had when non-default values are set

elasticdog: rather than specify -j1, I simply unset the variable from makepkg.conf so whatever cjd sets is used instead- let me know if you continue to have issues, and thanks for reporting!

elasticdog commented on 2013-08-08 06:15

I think you'll want to add `export MAKEFLAGS="-j1"` to the build() section in order to prevent issues with compilation (re: I had my MAKEFLAGS set to -j8 in /etc/makepkg.conf on and kept having trouble compiling the package due to odd failures.

prurigro commented on 2013-08-05 17:27

CJD fixed the cmake stuff for >=2.8.11, so I've updated the package to remove my conditional hack since it works regardless of the conditions now.

Kido commented on 2013-08-02 01:40

Cant build it.

First there is this:

[ 6%] Building C object util/version/CMakeFiles/cjdns-util-version-version.dir/Version.c.o
In file included from /tmp/yaourt-tmp-kido/aur-cjdns-git/src/cjdns/util/events/libuv/Time.c:18:0:
/tmp/yaourt-tmp-kido/aur-cjdns-git/src/cjdns/util/events/libuv/EventBase_pvt.h:22:16: fatal error: uv.h: No such file or directory
#include <uv.h>
compilation terminated.
make[2]: *** [util/events/libuv/CMakeFiles/cjdns-util-events-libuv-time.dir/Time.c.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Building C object crypto/random/test/CMakeFiles/cjdns-crypto-random-test.dir/DeterminentRandomSeed.c.o
Linking C static library libcjdns-util-log.a
[ 7%] [ 8%] In file included from /tmp/yaourt-tmp-kido/aur-cjdns-git/src/cjdns/util/events/libuv/Timeout.c:16:0:
/tmp/yaourt-tmp-kido/aur-cjdns-git/src/cjdns/util/events/libuv/EventBase_pvt.h:22:16: fatal error: uv.h: No such file or directory
#include <uv.h>
compilation terminated.
make[2]: *** [util/events/libuv/CMakeFiles/cjdns-util-events-libuv-time.dir/Timeout.c.o] Error 1
make[1]: *** [util/events/libuv/CMakeFiles/cjdns-util-events-libuv-time.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

Fnd in the end of build is this:

[ 16%] Built target libuv_ep
make: *** [all] Error 2
Failed to build cjdns.
==> Entering fakeroot environment...
==> Starting package()...
install: cannot stat ‘/tmp/yaourt-tmp-kido/aur-cjdns-git/src/cjdns/build/admin/angel/cjdroute2’: No such file or directory
==> ERROR: A failure occurred in package().
==> ERROR: Makepkg was unable to build cjdns-git.

prurigro commented on 2013-08-01 06:34

Package Update!

* The PKGBUILD has been cleaned up a bit more, and I fixed a few small things with the help of namecap (good call facecool)
* The install script now warns a user when they don't have python2 installed, and explains that certain scripts won't work without it (to reduce confusion)
* A new patch has been included that sets the 'do' script to allow the current archlinux version of cmake rather than compiling 2.8.8 itself, and it's applied when libnacl is installed. (The 'do' script fails when cmake 2.8.11 tries to build nacl)

I think that's all for now- cheers!

prurigro commented on 2013-08-01 01:29

facecool: Hey there! I double checked and can confirm that I'm also running cmake on my system, and running ./do to build cjdns definitely still downloads cmake 2.8.8 to use instead of the system one. To confirm that is indeed still broken (since it was my patch that removed it from the whitelist originally:, I temporarily whitelisted 2.8.11* in ./do and ran the script, which promptly failed during the nacl portion of the build. I decided to see what would happen if I installed libnacl to bypass its portion of the build process, and this time everything builds successfully! Apparently only the nacl portion is broken.

Now that said, I've weighed the pros and cons of setting nacl as a dependency, and I feel like explicitly setting it makes some assumptions about the user's needs. It also means that if an updated libnacl is released that breaks compatibility with cjdns, everyone on arch is going to break until this can be resolved, rather than only those with libnacl installed... That said, I do like the idea of making fast compile times possible again for those with a compatible configuration, so I'm going to try and make it so the internal cmake will be used when libnacl is installed along with the next release.

As for the python2 stuff- I've asked around to see how others using the package feel, and everyone I've talked to so far has wanted to keep python2 as an optional dependency. In respect to a split package solution to make everyone happy, I've actually been maintaining one on gitboria alongside this (hence the package() function being split into functions by category.) Now you might have more up to date information than me regarding some workaround using $PKGBASE, but last I'd checked the AUR wasn't able to parse split packages to have them included (they'd fail on attempted upload). I haven't attempted to try again quite yet, but I did check back at the (now infamous) bug thread on the matter though ( and it seems like people are suggesting solutions that take advantage of $PKGBASE, but there's been no followup about an attempt at implementing one of these ideas, and the bug is still marked open. If you have some information I haven't been able to find on the matter though, that would preferably work without any ugly hacks, I'd love to hear it- a single split package would definitely be preferable to maintain :)

Are you available on IRC (preferably efnet, freenode or hypeirc) or xmpp? I feel like discussing this in real time might be beneficial if it's possible :)

facecool commented on 2013-07-29 13:18

Namcap (pacman -Si namcap) is a pacman package analyzer which aims to find errors made during package building.

In order to satisfy various set of systems you may use pkgbase ( to build a split set of packages. This will help to build lightweight packages aside of full versions. But you will need python2 as makedepends anyway.

As for my system arch's native cmake ( was able to build a cjdns binaries. Currently testing them on virtual machine.

prurigro commented on 2013-07-29 12:31

Also, what do you mean in regards to namecap?

prurigro commented on 2013-07-29 12:29

Hi facecool, thanks for the patch!

The reason cmake isn't included in the makedepends is because the current version included in arch (2.8.11) uses different syntax than the cmake cjdns was written for (>2.8.10 iirc), and while cjd is rewriting the build process using node because of this, you'd need an older version of cmake installed or the package will simply build one on it's own anyway at the moment. On a side note, you can skip building nacl if you install a compatible version of that, too.

As for the python2 stuff... The python2 package is pretty big for smaller systems (~65 megs), so while I wanted to provide the python2 scripts, I didn't want to make python2 a requirement either. I figured I'd make it simple for people to comment support out completely if they didn't want the scripts built into the package at all (by commenting out the function that includes them in the package function), and I made python2 an optional dependency so it could be added at any time after to enable support for those scripts (or even temporarily at a point when they're needed), but your right about this being a bit confusing when you install and find they don't work... Thoughts on how this might be done better?

Also, do you think it's worth using python2 to set the path? Do people use different directories that would make this a worthwhile thing to do?

facecool commented on 2013-07-29 08:49


Python related stuff currently does not work out of the box. There are also several violations during namcap check. Please consider this PKGBUILD patch

prurigro commented on 2013-06-14 14:53

Package updated!

* The python stuff and have been tweaked to work again

* There are now a bunch more utilities included in the package, all starting with cjdns-* (but following their original names after that)

* In the name of keeping standard with upstream, /etc/conf.d/cjdns has been moved to /etc/default/cjdns-- please backup your config before updating if you changed it at all from the default settings!

Please comment if anyone finds themselves having any issues!

prurigro commented on 2013-06-14 11:42

latest update broke the package-- give me a few while I test the replacement

jecxjo commented on 2013-06-01 05:52

I could have previously confirmed armv6h support but as I've formatted my Raspberry Pi and now am having these compiling issues I cannot. I will update the thread once I get it working.

prurigro commented on 2013-05-27 07:10

As jecxjo brought to light, cmake 2.8.11 doesn't work with the cmake build files used by cnacl (and possibly cjdns). I submitted a pull request that cjd's accepted to prevent the ./do script from using the system cmake if the version is greater than 2.8.10, and have updated the package to use the ./do script again until cjd updates cnacl (and possibly cjdns) to comply with the latest cmake's syntax.

Aside from the above, the update has removed cmake from the makedepends array, and added armv6h to the arch array (someone correct me if this shouldn't be the case)

A number of changes to the cjdns sources were pushed just as I updated this package (I had to wait for these before my pull request was accepted), so the update is worthwhile for everyone.


prurigro commented on 2013-05-27 02:55

jecxjo: issue confirmed, caused by the update to cmake 2.8.11; let me ask cjd about a fix, otherwise I'll have the build use an older cmake like the ./do script

prurigro commented on 2013-05-27 02:21

jecxjo: Ahoy there-- there haven't been any updates recently so I haven't tried building for while now, but let me try again tonight and report back.

jecxjo commented on 2013-05-27 00:31

Removed my previous comment for a better one. Looks like nacl still has compiling issues with GCC 4.8.0. I've tried this on both an x86_64 and an armv6h system with the same failure.

jecxjo commented on 2013-05-26 18:50

Seems the Nacl bug isn't fixed. Tried it both on x86_64 and armv6h and neither built nacl_ep. Tried aur/nacl as well and of course that causes other compile issues with cjdns.

prurigro commented on 2013-05-03 05:11

Nice! Nacl compile bug has been fixed by cjd and the package has been updated to grab branch=master again :)

prurigro commented on 2013-04-30 09:53

Alright, the package has been updated! Unfortunately, I somehow managed to version the previous package using the latest (incompatible) value (0.3.1149), so this will cause issues triggering an automatic update via yaourt for anyone who installed that since as far as yaourt knows, your current version is newer than this one.

That said, all the required changes I can think of have been made, a lot of small issues I noticed as I went through have been fixed, and I reworked a few items for clarity and cleanliness.

I also realized that building with NO_DEBUG means there aren't any debugging symbols we don't want stripped out anymore, and so I've re-enabled the makepkg.conf OPTIONS variable for now.

Feel free to let me know if anyone notices anything else they think should be changed!

prurigro commented on 2013-04-30 08:52

The next release will unset conflicting makepkg.conf variables using the unset command instead of having them ="", and this will now be done in build() rather than mixing the declarations with package variables like before.

Interestingly, I actually discovered a series of warnings that were popping up because of the makepkg.conf CPPFLAGS variable (which I hadn't previously touched), and they quickly disappeared when I unset this as well.

I've also moved the sysvinit files to github as per Xyne's recommendation, and will be uploading the updated package with the aformentioned changes as well as a few other tweaks in a minute or two.

prurigro commented on 2013-04-30 07:03

djpohly: Good to know and thanks for reporting! I'll update the explanation to reflect that there aren't currently any known failures caused by overriding cjd's optimizations with the generic ones makepkg defaults to use. That said, everyone should keep in mind that when cjd recommended I unset the makepkg default CFLAGS and such in this package, it was because he felt his were/are the correct ones to use when building regardless of whether or not setting any others caused a problem.

djpohly commented on 2013-04-29 21:35

For what it's worth, I just built successfully here on x86_64, 100% tests passed, without resetting CFLAGS or OPTIONS (and nothing non-default specified in .makepkg.conf).

prurigro commented on 2013-04-29 21:16

Xyne: Sweet, thanks! I was trying to find a way to do it directly in the URL last night, but I'd already cut into my sleep time making your changes before finding out about the nacl issue and figured a hack solution would be better than a broken package. I'm glad you knew how to sort it out properly anyway :) (just about to upload the updated PKGBUILD)

Also, in respect to included source files-- I guess I hadn't thought about supplimentary bash scripts specific to arch as 'source files' before, but if you think it could cause any issues I'll setup a git repo and source from that sometime soon.


Xyne commented on 2013-04-29 20:24

Thanks for incorporating the changes. I noticed that you are resetting the head in the pkgver() function. This is the wrong way to do it. The only function that should modify VCS sources is the prepare() function, but even that should only be used for patching and other custom modifications. To checkout a specific commit, replace "branch=master" with "commit=<id>" in the sources array. For example, in this case you should use "commit=9c556ebf84".

You should also strongly encourage your friends on hyperboria to upgrade to systemd. There is not much of a point to running an outdated Arch system. That, however, was not the only reason that I removed the old daemon from the package. AUR packages should not contain any source files. Their presence can be grounds for deletion and some TUs will delete such packages on sight, so I recommend that you update the package to conform to the rules as soon as possible.

Thanks again!

prurigro commented on 2013-04-29 08:38

Alright, I've created an updated package using Xyne's submission as a reference.

I'd eventually like to make this into a split package with cjdns-git containing the core binaries and systemd service, cjdns-sysvinit containing the legacy rc.d and conf.d files, and cjdns-log containing the cjdnslog script and associated python libs; however, the AUR currently doesn't support split packages, and being that I currently know numerous Arch users on Hyperboria who still rely on the sysvinit script because they haven't upgraded their systems to use systemd, I'm not going to remove support quite yet... That said, I've split the contents of package() into three functions, each associated with the three ideas I mentioned above, and you can just comment out the line where the associated function is called in package() if you want to remove specific functionality like sysvinit.

Xyne: I didn't copy your package verbatim for a variety of reasons, but definitely let me know if you notice any of your changes that I didn't implement which happen to be required for conforming to Pacman 4.1 VCS or something (maybe if you think they work much better your way or something too)

Everyone should take note that this release has been set to use the commit prior to the one where CJD updates to the latest nacl (which currently fails to build on most configurations.) I'll switch back to the latest HEAD once I either figure out how to get things to compile or CJD commits a fix, but if you notice a fix has been posted before I update, want to see if your system is able to build things the way they are, or want the package to use the latest HEAD for any other reason, just comment out or remove the following line: "git reset --hard 9c556ebf84 #Set HEAD back to older commit, before nacl started causing issues with compiling"


prurigro commented on 2013-04-28 09:02

Xyne: Ahoy there! I have the package resetting CFLAGS because prior to doing this, the default CFLAGS set by Arch caused the cjdns tests to fail, and being that CJD sets his own CFLAGS in the cmake, resetting the Arch ones isn't going to leave the package optimization free or anything bad like that. Thanks for taking a look at the PKGBUILD on that note-- I'll see what changes you've made after posting this, and throw up an updated package based on your changes.

On a side note, I've started to maintain a split PKGBUILD in Gitboria that will continue any changes here except split the package into the main items, the rc.d stuff (for those who haven't updated to systemd, and the cjdnslog stuff, which requries python2. Everything is included in this package, since the AUR doesn't allow split packages unfortunately; when I post my next update I'll leave a link to where the split PKGBUILD is hosted on gitboria.


Xyne commented on 2013-04-25 19:59


I have updated the PKGBUILD to conform to Pacman 4.1 VCS packages. I have also removed redundant makedepends (base-devel packages should not be included, even if I myself prefer explicit deps) and simplified the build and package functions.

I have also removed the deprecated init.d-style daemon.

I suspect that CFLAGS and OPTIONS do not need to be reset, but I have not removed those lines because I am not familiar enough with the package yet to understand why they were reset in the first place.

You can get the updated PKGBUILD here:

Thanks for maintaining this package.


prurigro commented on 2013-04-24 21:53

2 fixes thanks to werecat: cjdns.service is now being grabbed from the git repo, and the license metadata for the package is GPL3 instead of GPLv3 (GPL3 is correct)

I've also added cmake to the build deps

prurigro commented on 2013-04-24 07:50

Yay, she builds with GCC 4.8.0 now! (If you need to enable debugging support, disable the -O2 optimization flag as a bug in GCC 4.8.0 causes the build to fail when both are set)

prurigro commented on 2013-02-21 08:59

python2 is now an optional dep for more lightweight systems, though you won't be able to use cjdnslog without it.

prurigro commented on 2013-02-05 23:46

Just a little fix to prevent '/etc/rc.d/cjdns start' from spitting out a bunch of text when run

prurigro commented on 2013-02-02 22:03

Updated deps and updated upgrade script (everyone should upgdate cjdns anyway if they haven't done so recently!)

prurigro commented on 2012-11-16 13:04

Turns out that using instead of means cjdns wont start on boot despite being enabled using certain network init setups, and so I've changed things back to for the moment.

prurigro commented on 2012-11-11 15:30

Dropped the sqlite3 dependency

prurigro commented on 2012-11-11 15:28

Set cjdns to a dependency of as recommended by Horazont

prurigro commented on 2012-11-11 15:09

Grawity gave me a hand improving the systemd unit file (thanks!), and it no longer relies on an external script, the sysvinit config file, or cron to work and restart cjdns if the process fails.

prurigro commented on 2012-11-11 06:02

I fogot to mention that I got rid of that pesky systemd bug on sysvinit boxen :)

prurigro commented on 2012-11-11 05:48

Removed cjdadmin because its been getting buggy and I haven't been updating it; cjdns-tool does everything it did much more quickly if you're after the same functionality.

The script is now used by both the sysvinit (/etc/rc.d/cjdns) and systemd (/usr/lib/systemd/system/cjdns.service) service scripts, and instructions have been included that describe how to add a cron job that will use to restart cjdns if it fails. (They're in cjdns-git.install if you miss them after upgrading)

The /etc/conf.d/cjdns environment script has been edited heavily to match and override the variables used in, so make sure you merge these after upgrading.


prurigro commented on 2012-11-02 08:34

Whoops- somehow the patch line had duplicated itself, I thought my server was missing patch but it actually just didn't like being called as its own input; this should sort things out :)

prurigro commented on 2012-11-02 08:29

*Added patch to makedepends

prurigro commented on 2012-11-02 08:06

This upate:
*Adds the python support modules for cjdns admin scripts written in python, and cjdnslog for viewing cjdns logs (run to view setup instructions)
*Patches cjdnslog to use python2 (as intended) rather than python3 (through the python symlink) until my pull request has been accepted
*Fixes an annoyance that caused systemd to be triggered when upgrading the package on systems that don't use systemd

prurigro commented on 2012-11-02 08:05

This upate:
Adds the python support modules for cjdns admin scripts written in python, and cjdnslog for viewing cjdns logs (run to view setup instructions)
Patches cjdnslog to use python2 (as intended) rather than python3 (through the python symlink) until my pull request has been accepted
Fixes an annoyance that caused systemd to be triggered when upgrading the package on systems that don't use systemd

prurigro commented on 2012-10-30 11:08

There, along with a few small tweaks, the PKGBUILD now cleans the appropriate files before running 'git pull' rather than deleting and cloning- I hope this helps save bandwidth for when it counts! :)

prurigro commented on 2012-10-27 22:48

Hi grawity, this was a measure I added a while back as a lazy solution to a problem I was running into and to be honest, with unlimited bandwidth I ended up forgetting to redo it properly. I might look into a proper solution sometime soon though, if the problem is even still there (and otherwise just make clean as usual.)


grawity commented on 2012-10-27 20:55

Why does the PKGBUILD remove and re-clone all repositories on every build? See what other -git packages do, and don't assume everyone has enough bandwidth to waste.

prurigro commented on 2012-10-23 00:54

*NOTE* those still using sysvinit: kill cjdroute manually before restarting if you upgrade first

prurigro commented on 2012-10-23 00:52

Updated for the new configuration. I'm pretty sure output is slated for stdout now, but nothing was appearing when I tested; if I find out differently and there's a way to capture output again I'll release an update.

prurigro commented on 2012-09-06 04:39

just a quick point release after TrueCrypt noticed that I'd included support for a reload with systemd via sighup (which isn't supported by cjdroute)

prurigro commented on 2012-09-06 04:23

Updated the init script based on the extra fun cjdroute currently requires, added systemd support (it uses systemd's own logsetup instead of the log directory in /etc/conf.d/cjdns), and the PKGBUILD has been cleaned up a bit including the removal of the webadmin stuff (upstream support has been gone for a while now) + it now compiles things as per the new ./do script to give upstream a bit more control over the method

d3x commented on 2012-08-15 07:25

y u so sexy prurigro

Anonymous comment on 2012-05-08 18:33

ok. thanks.


prurigro commented on 2012-05-07 02:23

Hi tintzin, cjd has removed the webserver until a scripting language version can be cooked up in its place. If you want admin server information for now, run the cjdamin script I've included and follow the instructions in the output :)

Anonymous comment on 2012-05-06 23:10

Is this a temporary anomaly due to git:

[root@tintzin ~]# /etc/rc.d/cjdwebadmin start
bash: /etc/rc.d/cjdwebadmin: No such file or directory

Or somethinfg else?
I was following the instructions here:


prurigro commented on 2012-02-12 11:05

Visit #cjdns on EFnet for more information :)