On Wednesday 13 January 2010 18:17:25 Moray Henderson (ICT) wrote: > Should I log the main issues in your bug tracker?
Yes, that is a very good idea. It is the only way to really ensure that the issues don't accidentally get lost -- especially since just now is a very intense period ... Regards, Kern > > > Moray. > "To err is human. To purr, feline" > > >-----Original Message----- > >From: Kern Sibbald [mailto:[email protected]] > >Sent: 13 January 2010 16:54 > >To: [email protected] > >Cc: Moray Henderson (ICT) > >Subject: Re: [Bacula-devel] Fedora/EL builds of 3.0.3 > > > >On Wednesday 13 January 2010 16:33:33 Moray Henderson (ICT) wrote: > >> Will there be a pre-release version of 5.0.0? I can certainly test a > >> CentOS 5 build and install. > > > >Even though pre-release testing is very useful and often finds > > problems, > > >in > >this case I don't think we will release a beta version because a good > >number > >of Bacula users have been running nightly regression tests, which we > >appreciate a lot. In addition, we are a bit limited on time, and the > > new > > >version requires a database upgrade, which once made you cannot go back > > to > > >3.0.x so not many users will be inclined to test in a real production > >environment. > > > >For testing, probably the easiest it to git clone the repository. In > >structions are in the Developer's manual and also on the Bacula project > >pages > >of Source Forge. If you have spare cycles, you can also setup nightly > >regression testing, which is documented in the README.* files of the > >regress > >directory. > > > >> According to logwatch's CHANGES file, it was version 7 where they > >> changed to the new /etc/logwatch directory structure. > > > >OK, I am not sure what is going on with logwatch. I guess that is an > >additional feature that one of the packagers (probably Scott) setup. > > > >The log rotation code, which I don't think you are referring to, that I > >setup > >a very long time ago is a simple file (not a script) that goes > >in /etc/logrotate.d. So I will have to take a closer look at what is > >going > >wrong in the spec file. > > > >Best regards, > > > >Kern > > > >> Moray. > >> "To err is human. To purr, feline" > >> > >> >-----Original Message----- > >> >From: Kern Sibbald [mailto:[email protected]] > >> >Sent: 13 January 2010 14:51 > >> >To: Philipp Storz > >> >Cc: [email protected] > >> >Subject: Re: [Bacula-devel] Fedora/EL builds of 3.0.3 > >> > > >> >On Wednesday 13 January 2010 15:40:28 Philipp Storz wrote: > >> >> Hello list, > >> >> > >> >> I put Kern's spec files into the opensuse build service, into my > > home > > >> >> project, > >> >> > >> >> where they build successfully on > >> >> CentOS_5 > >> >> Fedora_10 Fedora_11 Fedora_9 > >> >> RHEL_4 RHEL_5 > >> >> SLES_9 SLE_10 SLE_11 openSUSE_11.0 > >> > >> openSUSE_11.1 > >> > >> >and openSUSE_11.2 > >> > > >> >Yes, the fact that we have so many different platforms for which the > >> >packagers > >> >build complicates considerably the problems. Hopefully something > > like > > >> >this > >> >and a few testers will help us improve the features and quality of > > the > > >> >packages. > >> > > >> >> I would like to improve the packages there. > >> >> > >> >> Everybody who wants to help, just has to get his free obs account > > on > > >> >> https://build.opensuse.org/ > >> >> and then I can add him to the project. > >> >> > >> >> One thing that I did is that I reduced the size of the > >> >> bacula-docs-3.0.3.tar.bz2 from 50 to 30 Megabytes by using > > "fdupes", > > >> as > >> > >> >> there are many duplicate files in the different languages. > >> >> > >> >> What we need most in my opinion is testing of the rpms on the > >> > >> different > >> > >> >> platforms. > >> > > >> >Thanks for your help Philipp > >> > > >> >Best regards, > >> > > >> >Kern > >> > > >> >> Best regards, > >> >> > >> >> Philipp > >> >> > >> >> Am Dienstag 12 Januar 2010 16:40:32 schrieb Kern Sibbald: > >> >> > Hello, > >> >> > > >> >> > You might want to take a look at the new .spec files that I > > created > > >> >some > >> > > >> >> > time ago. I was hoping the packagers would use them for the > > 3.0.3 > > >> >> > release, but they used the old spec. I believe my spec files > >> > >> correct > >> > >> >> > most of these problems -- though the doc is still listed as > > tar.gz > > >> -- > >> > >> >> > that is easy enough to fix. > >> >> > > >> >> > Any feedback on these specs would be welcome, because they are > > the > > >> >specs > >> > > >> >> > that will be used to generate the next released version (5.0.0) > >> > >> which > >> > >> >> > should come around the end of this month. > >> >> > > >> >> > I have attached them here for your convenience. They are also > > in > > >> the > >> > >> >> > master branch of the SF git repo. > >> >> > > >> >> > Best regards, > >> >> > > >> >> > Kern > >> >> > > >> >> > On Tuesday 12 January 2010 16:12:59 Moray Henderson wrote: > >> >> > > Hello Developers, > >> >> > > > >> >> > > The platforms/redhat/bacula.spec.in file in your 3.0.3 tarball > >> > >> has a > >> > >> >> > > number of problems when built for EL5 and sqlite: > >> >> > > > >> >> > > - Source file bacula-docs is now bz2 not gz > >> >> > > - Logwatch location wrong for newer distros > >> >> > > - Logwatch applybaculadate script not installed > >> >> > > - Sqlite database not created with correct permissions > >> >> > > - Passwords not set up correctly in conf files > >> >> > > > >> >> > > Your published bacula-3.0.3-1.src.rpm fixes the first two, but > >> > >> not > >> > >> >the > >> > > >> >> > > remainder. > >> >> > > > >> >> > > The attached patch will ensure the correct logwatch locations > > for > > >> >the > >> > > >> >> > > supported Fedora-based distros (I don't know about SuSE or > >> > >> Mandrake) > >> > >> >as > >> > > >> >> > > well as fixing the other issues. > >> >> > > > >> >> > > I would also vote for having a placeholder in the Name fields > > of > > >> the > >> > >> >> > > .conf files, rather than the hostname of the build host. That > >> > >> way > >> > >> >the > >> > > >> >> > > real hostname can be inserted by the %post script in the same > > way > > >> >that > >> > > >> >> > > the passwords are. I'm building for CentOS 5, and will be > >> > > >> >installing > >> > > >> >> > > the rpms on several servers, so having all the resources named > >> > >> after > >> > >> >my > >> > > >> >> > > build server isn't very useful default. > >> >> > > > >> >> > > There's a small mistake in > > bacula-3.0.3/scripts/logwatch/README: > >> it > >> > >> >> > > tells you to copy scripts/logwatch/bacula to > > applybaculaupdate. > > >> >> > > I hope you find this useful. > >> >> > > > >> >> > > > >> >> > > Moray. > >> >> > > "To err is human. To purr, feline" > > > >----------------------------------------------------------------------- > > > >> --- > >> > >> >---- > >> >This SF.Net email is sponsored by the Verizon Developer Community > >> >Take advantage of Verizon's best-in-class app development support > >> >A streamlined, 14 day to market process makes app distribution fast > > and > > >> >easy > >> >Join now and get one step closer to millions of Verizon customers > >> >http://p.sf.net/sfu/verizon-dev2dev > >> >_______________________________________________ > >> >Bacula-devel mailing list > >> >[email protected] > >> >https://lists.sourceforge.net/lists/listinfo/bacula-devel > > ------------------------------------------------------------------------ > > >--- > > > >>--- This SF.Net email is sponsored by the Verizon Developer Community > >> Take advantage of Verizon's best-in-class app development support > >> A streamlined, 14 day to market process makes app distribution fast > > and > > >> easy Join now and get one step closer to millions of Verizon > > customers > > >> http://p.sf.net/sfu/verizon-dev2dev > >> _______________________________________________ > >> Bacula-devel mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/bacula-devel > > --------------------------------------------------------------------------- >--- This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Bacula-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bacula-devel ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
