[Pkg-gridengine-devel] SGE on Debian Unstable

[Dave Love]

Sorry for the delay, partly due to trying to get a new SGE release out.
The packaging will need fixing for that.

Laszlo Kajan <lkajan at rostlab.org> writes:

> Hello Michael, Dave, Tim, and other team members!
>
>> I've created a git repository on Alioth now, the repo URL is
>> git+ssh://git.debian.org/git/pkg-gridengine/pkg-gridengine.git
>> 
>> Anybody in the Alioth group should be able to push to it.
>
> I am not a git master -

I don't understand git...  I can probably do simple updates, though.

> just trying to learn it now. Another disclaimer: our group would like to continue to use SGE, but I, especially, am
> probably not capable of understanding its internals. My hope is that Dave would maintain his Debianization (for Debian), and therefore the
> Debian package, in Alioth and in the release.

There shouldn't be a problem maintaining packaging, but I don't seem to
understand enough about doing it.  I don't know where to find
authoritative information, and some of the stuff I have found is
inconsistent :-(.

> I do not aspire to become an SGE developer.
>
> 1: I imported (git clone --bare; git push --mirror) Mark Hymers' repository [1] to the new repo.
>
> 2: I do not expect any updates to Mark's repo. The new repo does not reference the old one in any way (now).
>
> 3: I imported (git-import-orig) Dave's current latest upstream snapshot [2] into upstream, filtering out his debian/ dir.
>
>  $ git-import-orig --verbose --filter sge-*/debian --pristine-tar --no-merge ../gridengine_8.1.3.orig.tar.gz

I was assuming only the packaging would be maintained there, producing a
debian.tar.gz which would just work with the sge distribution tarball.
Why does it need the whole tree there?

> 4: I configured Dave's 'gridengine.debian' git repo [3], as a remote. Hopefully Dave can maintain the
> Debianization in Alioth, though, instead of at [3].

I'm not sure about that, especially if it means maintaining an entire
source tree there too (when it gets changes to support the packaging, or
which affect it otherwise).

> 5: I loaded Dave's debian directory (with read-tree [4]) to debian-8.1.3, after removing the old debian dir.
>
> 6: I copied (not merged) upstream/8.1.3 to master git read-tree -m -u upstream/8.1.3

I don't know what that means...

> 7: libjemalloc-dev was missing during the build trial (debuild).

Do you mean there's a problem, or you just needed to install the
package?

> With that addition, source and binary builds were successful, though with
> lintian errors. We should build with git-buildpackage, though.

I didn't know what to do about the lintian errors, and my attempt to use
a lintian-overrides didn't suppress anything.  Some of the errors are
just wrong (e.g. binary without man page).  The man errors about wide
lines should probably just be ignored.  Some of them I just didn't
understand, like postinst-has-useless-call-to-ldconfig.  I don't know
why depending on fonts is wrong -- it's a common problem that qmon fails
without them.

Any guidance welcome!