On Wed, 2010-04-21 at 17:04 -0400, Matt White wrote: > I'm working on building 4.2 for Suse builds. > > Most of what I'm find is that builds are failing because newer suse > builds are far more strict in rpmlint. > > For example, sipxpbx fails because > "sipxecs does require services for start but nothing for stop" > > And sure enough the sipxecs.in file has > > Required-Stop: > > When Suse wants a > > Required-Stop: $null > > Should these fixes be included in the main builds?
If you'll test that they don't break the CentOS builds, patches are welcome (if whoever has to review the patch has to do it, integration will be _much_ slower). Open an issue and attach patches to it. Eric Varsanyi provided an excellent example of how to do this for F12 http://track.sipfoundry.org/browse/XX-7487 (I have many of those in a git repo and am trying to get the CentOS testing done, but it's slow). _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
