-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

> I already ha d deep look at the current packaging included in upstream git, 
> basically the initscripts need to be rewritten as they are full of 
> redhadisms, but thats'it basically. 

As far as I can tell, the packaging in upstream git (and upstream tarballs) is a
not-quite-up-to-date copy of the Ubuntu packaging for ocfs2-tools 1.3.9. I 
disagree about
rewriting the initscripts, until now the init scripts shipped with Debian have 
always been
based on upstream with some minor Debian patches, and upstream has integrated 
all these
patches. As time is short for lenny I'd rather stick to well-tested upstream 
init scripts.

> I think the debconf templates and the corresponding configuration parts in 
> the 
> maintainer scripts should be removed for Lenny, because I doubt we would get 
> this into testing in time, lacking all translations. It's broken anyway, and 
> I currently have no time to fix that due to RL work overload.

In the Ubuntu packaging, the changes that were made were simply to update the 
default
values for timeouts. I have manually integrated these changes into all of 
Debian's
translations, so there should not be any translation issue. Are there any 
additional
changes to your knowledge?

> To your question, Alioth seems fine to me, but why not use oracle git, and 
> make it a native package?

I'd rather go the opposite way: ask upstream to drop the packaging in their git 
which is
not quite up to date, and encourage them (and Ubuntu maintainers) to contribute 
to the
packaging on alioth. Is there some cluster-related project on Alioth we can 
tack onto or
should I ask for a new project?

Cheers,
Jeremy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkmehcACgkQ4mJJZqJp2Sc5cQCeMvUAN88oBJSB0ade73pcuYBJ
Y4wAoKUVly1es2mDzbPOL2yLGzT9jqZH
=IJyT
-----END PGP SIGNATURE-----



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to