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
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.
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"
>
--
Philipp Storz [email protected]
dass IT GmbH Phone: +49.221.3565666-92
http://www.dass-IT.de/ Fax : +49.221.3565666-10
Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRB52500
GF: Stephan Dühr, Maik Außendorf, Jörg Steffens, Philipp Storz
------------------------------------------------------------------------------
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
