> On Mon, Aug 5, 2013 at 10:15 PM, Richard Hipp <d...@sqlite.org> wrote: > >> On Mon, Aug 5, 2013 at 3:55 PM, Benedikt Ahrens >> <benedikt.ahr...@gmx.net>wrote: >> >>> is not feasible in my situation. >>> >> >> packages or libraries or deal with package managers. Just copy *one file* >> into your $PATH on each machine where it matters. >> > > @Benedikt: the easiest thing to do is to edit your $PATH to include > $HOME/bin and drop fossil in $HOME/bin. If you need help with setting the > PATH, google for "ubuntu edit path" (bzw. "ubuntu path bearbeiten") and > several useful answers are there.
Thanks. However, my objection to upgrading to newer fossil was not motivated by a lack of know-how, but rather by the fact that this solution comes with a complexity of O(number of affected machines). Also, not all of the affected machines are mine. >> My question was intended to be "Can I do something to the >> >>> repository---and not to fossil---in order to get things working again, >>> with version 1.22?" >>> >> > We don't know, and that version is old enough for us to justify suggesting > you try a newer version before we pursue it further. It works fine with 1.26. BTW, is there any chance the Debian packaging could happen in a debian branch of the fossil development repository, i.e. that the Debian fossil maintainer get write access to that repo? Thanks for your help and patience. Benedikt [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718812 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
