Hello, On Monday 05 November 2007 18:12, Michael Short wrote: > Today I want to start a Restore job with Bacula 2.0.3 but it would > fail miserably after issuing a "status director" shortly after > starting the restore. I wasn't sure if this was a bug which was > already addressed, so I made my way to bugs.bacula.org to see if a > restore bug corresponded to my version of bacula. > > I proceeded to login, search for "restore", and was then presented > with results containing the word "result". However it is impossible to > sort this information in any way. There also didn't seem to be any > version specification on most of the bugs. Perhaps I am doing > something wrong here, but I think these issues should be addressed at > some point in the near future. >
Well, your request is a bit general, so I am not sure what you want us to do as you did not suggest any specific solution. I did take a look at the bugs list, and in the beginning very few people filled in the Bacula version or other information that we request. However, recently, nearly everyone fills it in. It is unpleasant and not very practical for us to constantly request users to put in information if it is not really critical, because it just delays the response and makes more work for us. I think our Bugs web page is pretty clear on what we need, and if we don't find the information we need, we sometimes either request it or close the bug and send the reporter back to the web page documentation. The ideal situation would be that everyone fills in everything and provides *all* the info we need, but this is not the case, and the problem is rather universal. When we supply a patch, the patch is very clearly labeled as to what version it applies, and if we fix a bug generally specify in which version it is fixed when we close the bug -- sometimes in the specific field provided, and sometimes as a bugnote, and sometimes both. A good resource for finding problems and fixes is the technotes or ChangeLog that are released with every version and kept current in the SVN. The SVN technotes are typically up to date, and it is really rare that we fail to mention a problem or a bug fix. As part of our effort to develop extensive professional support, at some time in the future we will have a more complete knowledge base, and I expect that to be much more easily searched. However, a knowledge base is very expensive to create and maintain (you have to pay people to do it), so I am not sure whether it will be available only to customers who pay for its creation and maintenance or to the general public. I'm not sure what more we can do. Kern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
