* Kern Sibbald schrieb am 10.09.07 um 18:49 Uhr:
> On Monday 10 September 2007 16:39, Ryan Novosielski wrote:
> > Kern Sibbald wrote:
> > > On Monday 10 September 2007 04:27, Ryan Novosielski wrote:
> > >> Kern Sibbald wrote:
> > >>> At this time, I do not have a patch for 2.0.x versions, and unless
> > >>> there is some really compelling reason to create one, I would prefer
> > >>> not -- it would not be a huge effort to back port the patch, but it
> > >>> would require rather extensive testing.  Though it is hard to make a
> > >>> specific recommendation, I believe that it probably will be the wisest
> > >>> and simplest to either patch version 2.2.x if that is what you are
> > >>> currently running, or upgrade to version 2.2.3 when it is released.
> > >>
> > >> My personal recommendation would be to release a patch to all versions
> > >> back to at 1.38.x if the bug can be verified. I know that not too many
> > >> people are running that version anymore, but if this bug is serious
> > >> enough that the software will not work, I would personally be worried
> > >> that someone will use one of these versions (the latest available of the
> > >> minor release, eg. the latest 1.38.x) and not know that this is a
> > >> problem.
> > >
> > > Yes, notifying users is a problem.  If they are not subscribed to either
> > > the bugs database or the announce list, they are out of luck :-(
> > >
> > > I'm considering adding a feature that the user could enable that would
> > > automatically notify him of critical problems, but that won't help in
> > > this case.
> >
> > The website would be another place. I also applaud the decision to
> > remove the affected versions for the time being. I guess the final risk
> > here now is installing many current distributions will get you an
> > affected version.
> 
> Yes, unfortunately.  Hopefully the downstream packagers are plugged into the 
> project.

I removed the affected packages from the packman repository as well.

-Marc

-- 
****************************************************
*   (morganj): 0 is false and 1 is true, correct?  *
*   (alec_eso): 1, morganj                         *
*   (morganj): bastard.                            *

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to