[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Sponsor request for gcvs



Hello,
No one wanted to sponsor my eol package, so I packaged up gcvs (which I couldn't find on dselect or by searching on debian.org (so I hope I'm not duplicating work). gcvs is a nice graphical front-end for cvs that uses gtk+ for it's gui. It shares the same codebase as wincvs and maccvs. The upstream is still an alpha version, but I've been using it for a while and find it pretty stable. My package can be downloaded from:
 <ftp://ftp.indigita.com/other/david/gcvs/> (.deb, .dsc, .diff, etc.)

I'm looking for someone to sponsor this package.
I'm also looking for a advocate so I can become a maintainer.

Lintian passes the source package with no error or warnings, but I get and error on the binary:

E: gcvs: interpreter-not-absolute ./usr/share/gcvs/ChangeRoot.tcl #!CVSGUI1.0
W: gcvs: script-not-executable ./usr/share/gcvs/ChangeRoot.tcl
W: gcvs: unusual-interpreter ./usr/share/gcvs/ChangeRoot.tcl #!CVSGUI1.0

Actually I get that error for every file in share/gcvs/*.tcl (18 files). It is all true, but I don't see why it's an error in this case. The scripts are used as macro extensions to the gui and are not runnable from the command line so the "script-not-executable" warning doesn't matter. Yes, in this case, "interpreter-not-absolute" is true and it is an "unusual-interpreter", I'll give it that :-).

But that's what this package uses to check if the script is the correct type. If that header is not there, then it won't run the script. I don't think I should patch the source to look for something different because this code is cross-platform and the tcl scripts need to run in both a linux environment and a mac/windows environment. So unless the mac code and windows code are also patched, the scripts need to stay the way they are.

All that being the case, how do I get lintian to shut up?

Or can someone see a way to get around this error?

-David

Attachment: pgpYJtBI9cuA1.pgp
Description: PGP signature


Reply to: