[csw-pkgsubmissions] newpkgs bacula, bacula_client, bacula_client_(...)

[Philip Brown]

On Sun, May 15, 2011 at 9:07 AM, Ben Walton <bwalton at opencsw.org> wrote:
>
> I'm not going to expend effort to support something that upstream
> deems obsolete.  Any update of this legacy package would also need
> modification to handle config migration, etc.  If _you_ have spare
> time to throw away on something like this, please do so.  I'll revise
> my package set to accommodate your bacula_gnome work when it's ready.
>
>> Please keep in mind that this isnt about "us", it's about our users.
>


Tell me Ben... what would you have done, if we were already in
"automated release to unstable", and someone filed a bug about this?
closed it with status "wonfix", so it migrates into current anyway?

What about if, as is more likely, no-one noticed it for 2 weeks, and
it made it into current directly... then someone filed a bug,
"Hey, I'm using 'current', not 'unstable', but you guys just
auto-removed a package I'm using? What's up with that???"

That is of course, presuming that they even COULD file a bug. because
once bacula_gnome is removed from the catalog, usual practice is to
disable the corresponding mantis areas also.