Bug#704484: solving the mod_vroot problem

Tomas Pospisek tpo at sourcepole.ch
Mon Apr 15 19:22:14 UTC 2013


Since this bug is wheezy RC, I'll try to contribute a little to solve it:

Francesco P. Lovergine wrote:

> Adam D. Barratt wrote:
>
>> mod_vroot used to be in proftpd-basic in squeeze, it's moved to a
>> separate package in wheezy.
>>
>
> and to be honest I would avoid to add proftpd-mod-vroot as a strict
> dependency. It is an optional (and experimental) module and the problem
> would be simply resolved by installing it by hand after a dist-upgrade.

One solution to this problem is to force installation of 
proftpd-mod-vroot. Either by depending on it or by merging the module back 
into the proftpd package. The module is very tiny:

   Compressed Size: 17.0 k
   Uncompressed Size: 85.0 k

relative to proftpd:

   Compressed Size: 2556 k
   Uncompressed Size: 4271 k

so from the packagesize/bloat point of view depending on the package 
doesn't really change much.

A weaker dependency would be to recommend it. Which would signal "only 
deselect the proftpd-mod-vroot package if you really know what you are 
doing" to the user. This option would pretty much keep the user safe from 
harm.

If you make proftpd only suggest the proftpd-mod-vroot or won't depend on 
it at all then I think that change should both be noted in the NEWS file 
and in the wheezy release notes.

Hope this helps 
*t



More information about the Pkg-proftpd-maintainers mailing list