>The postinst script unconditionally removes /etc/vserver{,s}.conf on
>every configuration. Since the configuration is apparently preserved
>by sourcing the files and creating a symlink in place of their
>content, this is okay. However the package both includes and removes
>the conffile vservers.conf which is not allowed.
I've removed in svn the conffile from the package. The functionality
has been provided by /etc/defaults/util-vserver.
>It's is also not okay if VSERVERS_ROOT and VSERVER_ROOT aren't the
>only things that were ever specified in those files, or if something
>else *could* have been (legitimately?) added there. Preferably the
>files aren't removed if anything else is there:
If you can find a real world example of this, I'd love to hear it, but
what you are talking about here is something like a potato migration to
sarge, the oldest tarball I could find of util-vserver only had in this
file things that have been moved to the defaults file.
> The same problem with these removals:
> |# Remove old startup scripts
> |rm -f /etc/init.d/vservers-legacy
> |rm -f /etc/init.d/vservers-default
> |rm -f /etc/init.d/vprocunhide
> |rm -f /etc/init.d/rebootmgr
These are startup scripts that have been rolled into one startup script,
not configuration files.
> |rm -f /etc/default/util-vservere
This was a legacy mistake and never had anything in it.
> There's another problem too: removal of the symlinks isn't preserved:
> run.rev vdirbase
Can you be a little more specific about this issue in a separate bug
report?
Micah
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
