October 2009 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] audit 2.0 packaging question
by Tony Jones 02 Oct '09

02 Oct '09

[I'm not suggesting any of this for OpenSUSE 11.2 ;-)] audit 2.0 has been released. Removal of dead/broken apis with the result that libaudit.so is now bumped to .1 A while ago it was deemed necessary for audit to be split into two spec files, audit.spec and audit-secondary.spec to move python dependancies to prevent huge build system dependancies. Not sure if this is still needed?? If not it would be nice to go back to just one spec as it makes updates a bit easier. To the more important question .... I can osc build v2.0 of audit.spec which produces libaudit.so.1 but when I try to build audit-secondary using previous as the preferred rpms the buildsystem fails to init because su, pam, others require that something provides libaudit.so.0. I have the changes checked into: https://build.opensuse.org/package/show?package=audit-secondary&project=hom… I briefly talked to Marcus on IRC about whether we needed to provide a compat library and he didn't think it was necessary as most/all users of audit-libs are suse system rpms but Adrian seemed to be of the opinion that it was essential for things to build inside the Factory buildservice. Right now my interest is just getting the above location building for test purposes. Not sure if there is an easy way? I can force load the resultant new audit-libs.rpm over an existing system for testing but I'd like to test the -secondary stuff also. Tony -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 8

[opensuse-packaging] enabling services while installing a package
by Stefan Schubert 02 Oct '09

02 Oct '09

Hi, we have a WebYaST plugin called "status" which will be installed via an own RPM (yast2-webservice-status). This plugin requires a running service collectd (package collectd). So how is the correct way to enable and start collectd while installing yast2-webservice-status. My first assumption was: File: yast2-webservice-status.spec: PreReq: collectd %post # # enable and start collectd # insserv -f collectd /etc/init.d/collectd start Is this the correct way, or not ? Thank you and greetings Stefan -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] BuildRequires rpms from other repos
by aledr 02 Oct '09

02 Oct '09

Good day! I need to provide python-protobuf (from protobuf in devel:tools:building) and python-ReportLab (dropped from openSUSE:Factory but availabe in openSUSE:Factory:Contrib) as BuildRequires for two packages in devel:languages:python. Should I just link these packages into devel:languages:python or add its entire repo under Build Repositories? Seems that first makes more sense to me. Regards. -- [ ]'s Aledr - Alexandre "OpenSource Solutions for SmallBusiness Problems" -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 7