[Nut-upsdev] CENTOS 6.6 NUT RPM BUILD ISSUES

[Jim Klimov]

24 марта 2015 г. 0:57:22 CET, Eric Cobb <Eric_Cobb at tripplite.com> пишет:
>Charles,
>
>I need so major help with getting development build working and need
>some assistance. Here are the issues that we are running into:
>
>Number 1 change - 2.7.2 no longer has the HAL scripts that 2.6.5 has.  
>I am working on if HAL is actually required on CentOS6.6 with the 2.7.2
>code or if they have another way around it.  This is code diving which
>is taking some time.
>
>Number 2 change  -
>RPM build errors:
>    Installed (but unpackaged) file(s) found:
>   /usr/bin/nut-scanner
>   /usr/sbin/upsdrvctl
>   A dozen + Man pages
>
>You mentioned the following a couple of weeks ago:
>
>I haven't really used RedHat products regularly since before they
>started the Fedora project, but from what I understand, it should still
>be possible to grab the SRPM for NUT, extract it to /usr/src, change
>the version number to 2.7.whatever, rebuild the binary RPMs, and
>reinstall.
>
>I am really a newbie when it comes to the building of packages. Where
>do I get that SRPM for the NUT version that will work with the
>SMART500RT1U? Does anyone have a RPM of 2.7.2.6 that is built for
>Centos 6.6 that I could try?
>
>Here is the environment-
>OS: Centos 6.6
>Kernel: 2.6.32-504.8.1.el6.x86_64
>Nut Version: nut-2.6.5-2.el6.x86_64
>
>
>Eric K. Cobb
>Product Management Specialist
>
>[Tripp Lite]
>
>1111 W. 35th Street   |   Chicago IL 60609 USA
>773.869.1203   |   Fax 773.869.1935
>website<http://www.tripplite.com/EN/index.cfm>  | 
>email<mailto:eric_cobb at tripplite.com>  |
>
>[Reach Me on Skype]<eric.cobb21>  [Follow us on Twitter]
><http://twitter.com/tripplite>   [Find us on Facebook]
><http://www.facebook.com/TrippLite>   [See us on YouTube]
><http://www.youtube.com/profile?user=tripplite>   [Find us on Linkedin]
><http://www.linkedin.com/company/tripp-lite>
>
>
>
>This message is for the addressee´s use only. It may contain
>confidential information. If you receive this message in error, please
>delete it and notify the sender. Tripp Lite disclaims all warranties
>and liabilities, and assumes no responsibility for viruses which may
>infect an email sent to you from Tripp Lite and which damage your
>electronic systems or information. It is your responsibility to
>maintain virus detection systems to prevent damage to your electronic
>systems and information.
>
>
>
>________________________________
>This message is for the addressee's use only. It may contain
>confidential information. If you receive this message in error, please
>delete it and notify the sender. Tripp Lite disclaims all warranties
>and liabilities, and assumes no responsibility for viruses which may
>infect an email sent to you from Tripp Lite and which damage your
>electronic systems or information. It is your responsibility to
>maintain virus detection systems to prevent damage to your electronic
>systems and information.
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Nut-upsdev mailing list
>Nut-upsdev at lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

Hello Eric, use google-fu! ;)

Generally, you take your needed package name to google and add srpm. Then you come up with the great rpmfind resource and either sources for your package http://www.rpmfind.net//linux/RPM/epel/6/x86_64/nut-2.6.5-2.el6.x86_64.html or for others in the family http://www.rpmfind.net/linux/rpm2html/search.php?query=nut - for example, on top of the list you see packages for 2.7.2

You download an .srpm (or a .src.rpm) file and can use rpmbuild program to build your binary version (-ba flags iirc) or to unpack and fiddle in the sources. At the core of rpm packages are spec-files which include the package metadata as well as references to dependencies, upstream sources and an ordered list of optional patches (copy of code and patches are usually included alongside a spec-file and form the srpm content), the ways to configure and build the code, and the list of installable files (should be 1:1 to the structure of your temporary installation directory for the build products).

Good luck, and I hope this helps!
//Jim Klimov 
--
Typos courtesy of K-9 Mail on my Samsung Android