Edward Bartolo <edbarx@???> writes:
> I applied the patch suggested yesterday by Rainer *manually* by
> editing files. I am lost here and I am hesitant to mess with git as it
> can easily damage my sources.

While I have some "areas of disagreement" with git, it isn't that
bad. In particular, you can always use it to restore something to a
prior state. For the given problem, you could start with creating a
branch for "debianization changes " and run dh_make on the branch and do
any other ".deb-changes" there. This would enable easy generation of
both an upstream tarball and some "debian patches".

But that's still a bit early as the public git-tree still doesn't compile:

backend.pas(100,13) Error: Identifier not found "RunCommand"
backend.pas(109,19) Warning: Local variable "s" does not seem to be initialized
backend.pas(129,15) Error: Identifier not found "RunCommand"
backend.pas(214,15) Error: Identifier not found "RunCommand"
backend.pas(217,21) Warning: Local variable "s" does not seem to be initialized
backend.pas(241,15) Error: Identifier not found "RunCommand"
backend.pas(244,21) Warning: Local variable "s" does not seem to be initialized
backend.pas(264,15) Error: Identifier not found "RunCommand"
backend.pas(266,35) Warning: Local variable "s" does not seem to be initialized
backend.pas(274,15) Error: Identifier not found "RunCommand"
backend.pas(277,26) Warning: Local variable "s" does not seem to be initialized
backend.pas(346,47) Hint: Local variable "Buffer" does not seem to be initialized
backend.pas(535) Fatal: There were 6 errors compiling module, stopping

A procedure RunCommand isn't defined by anything. This might be caused
by a file which exists only in your local copy and not in git.