Package: munge
Version: 0.5.10-1
Severity: wishlist
Hi,
I have local packages that contain netboot images for diskless cluster with
various configurations. Among them are images that use torque and slurm,
both of which depend on munge. For security reasons each installation of
those images should have their own munge.key file, which should be generated
(if missing) in postinstall and then copied into each new image.
For that the image packages need a "Depends: munge" just so create-munge-key
is available if needed. But that means that suddenly the boot server also
becomes a munged server. It would be better if I could depend on just the
create-munge-key tool.
So please split create-munge-key into a seperate package, e.g. munge-utils.
MfG
Goswin
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
