Are install/makepack script broken?
I run it and I got following output:
$ export CHECKLIBGDB=no
$ export NOGDB=1
$ touch ../doc-pdf.tar.gz
$./makepack
...
Copying install.sh
Creating binary.x86_64-linux.tar
tar: units*.x86_64-linux.tar.gz: Cannot stat: No such file or directory
tar: Exiting with
Hi,
If you are interested in a FPC-based GPL-ed git frontend, MSEgit 1.0 has been
released.
Binaries:
https://sourceforge.net/projects/mseuniverse/files/msegit/1_0/
Screenshots:
https://sourceforge.net/projects/mseuniverse/
Source:
http://gitorious.org/mseuniverse/mseuniverse/trees/master/tool
waldo kitty schrieb:
> ummm... speaking as one who has fought the spammers and won their
mailbox back from them, this is much bovine fecal material... i have
fought "them" from +1000/day spams back to less than ~5/day... it is
very possible but one nes to stay vigilant and report the spams to t
In our previous episode, Thierry B. said:
> >> So I just try your advice. Builds :
> >> - 2.6.0 from 2.4.5 : oops, not 2.4.4 but it is : OK
> >> - 2.6.1 from 2.6.0 : NOK : __missing_command_DATA2INC -b -s fppkg.cfg
> >> fppkg.inc fppkg
> >>
> >> same error, so there is something wrong with 2.6.1
>
Le 12/03/2012 01:38, Jonas Maebe a écrit :
On 11 Mar 2012, at 22:07, Thierry B. wrote:
So I just try your advice. Builds :
- 2.6.0 from 2.4.5 : oops, not 2.4.4 but it is : OK
- 2.6.1 from 2.6.0 : NOK : __missing_command_DATA2INC -b -s fppkg.cfg fppkg.inc
fppkg
same error, so there is somethi
