search for: showrc

...d need to define it in youe rpmbild line AND your rpm signature line. >> >> Are you building your rpms in mock or from rpmbuild on the command line? >> >> If I do this on my default c7 install, I get that as the default: >> >> [jhughes at localhost ~]$ rpmbuild --showrc | grep filedigest_algorithm >> -14: _binary_filedigest_algorithm 8 >> -14: _source_filedigest_algorithm 8 >> >> Not sure how you got it to do it in SHA1 :) > > One last thought .. are you using something like: > > --force-v3-sigs > > in your signing comm...

Hi All, Currently my system is using httpd 2.2.27. As there were many Vulnerability fixes released under 2.2.29, I would like to upgrade the Apache httpd. My system is having CentOS 6.5. I checked on CentOS Repos using yum but could not find the latest httpd rpm from there. So I am building the httpd rpm from the source tar ball downloaded from apache site. I am able to build the rpm successfully

...mmacros would be best .. I think otherwise you would need to define it in youe rpmbild line AND your rpm signature line. Are you building your rpms in mock or from rpmbuild on the command line? If I do this on my default c7 install, I get that as the default: [jhughes at localhost ~]$ rpmbuild --showrc | grep filedigest_algorithm -14: _binary_filedigest_algorithm 8 -14: _source_filedigest_algorithm 8 Not sure how you got it to do it in SHA1 :) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc...

...ipt. It will generate a RedHat compatible rpm for you. I had to make these changes to it though: --8<------------------------(Cut Here)----------------------------------- --- makerpms.sh.orig Mon Dec 14 22:52:41 1998 +++ makerpms.sh Tue Dec 15 17:42:30 1998 @@ -5,10 +5,10 @@ SPECDIR=`rpm --showrc | awk '/^specdir/ { print $3}'` SRCDIR=`rpm --showrc | awk '/^sourcedir/ { print $3}'` -( cd ../../.. ; tar czvf ${SRCDIR}/samba-2.0.0beta4.tar.gz samba-2.0.0beta4 ) +( cd ../../.. ; chown -R root.root samba-2.0.0beta4; tar czvf ${SRCDIR}/samba-2.0.0beta4.tar.gz samba-2.0.0beta4...

...oue rpmbild line AND your rpm signature line. >>> >>> Are you building your rpms in mock or from rpmbuild on the command line? >>> >>> If I do this on my default c7 install, I get that as the default: >>> >>> [jhughes at localhost ~]$ rpmbuild --showrc | grep filedigest_algorithm >>> -14: _binary_filedigest_algorithm 8 >>> -14: _source_filedigest_algorithm 8 >>> >>> Not sure how you got it to do it in SHA1 :) >> >> One last thought .. are you using something like: >> >> --force-v3-sigs &...

...e look it up here: https://access.redhat.com/security/cve/ And you will find the RH version that fixes the specific CVE. As to your original question, all CentOS RPMs are build using 'rpmbuild -ba <srpm>' in a chroot system called mock. If you look at the command "rpmbuild --showrc" you can see what is going to be passed in as variables: rpmbuild --showrc | grep ^optflags That is what would be passed into all packages .. plus whatever is set up in the SPEC file, which you can see from looking at it. All sources live on: http://vault.centos.org/ under the specific ver...

After updating a very old x86_64 3.x install to 3.8 it still has kernel-2.4.21-27.0.2.EL. Then if I repeat the yum update command, it offers to install kernel 2.4.21-47.EL.ia32e. Neither of these situations seems quite right. -- Les Mikesell lesmikesell at gmail.com

...herwise you > would need to define it in youe rpmbild line AND your rpm signature line. > > Are you building your rpms in mock or from rpmbuild on the command line? > > If I do this on my default c7 install, I get that as the default: > > [jhughes at localhost ~]$ rpmbuild --showrc | grep filedigest_algorithm > -14: _binary_filedigest_algorithm 8 > -14: _source_filedigest_algorithm 8 > > Not sure how you got it to do it in SHA1 :) One last thought .. are you using something like: --force-v3-sigs in your signing command line? -------------- next part --------...

...ine. >>>> >>>> Are you building your rpms in mock or from rpmbuild on the command >>>> line? >>>> >>>> If I do this on my default c7 install, I get that as the default: >>>> >>>> [jhughes at localhost ~]$ rpmbuild --showrc | grep filedigest_algorithm >>>> -14: _binary_filedigest_algorithm 8 >>>> -14: _source_filedigest_algorithm 8 >>>> >>>> Not sure how you got it to do it in SHA1 :) >>> >>> One last thought .. are you using something like: >&...

Hi, I need to get a spec file with all macro exanded, so i can extract info of some tags, that my be consitional based on macros, i know that some rpm utils need to make this to figure out dependencies and so on. I don't know if is posible to get a preprocesed spec file with actual Centos & rpm tools, if this is on librpm, i can make a simple tool to make this. Regards.

...ymbols* from ELF binaries when building packages with rpmbuild on CentOS? Seems that an out of the box rpmbuild install only discards debugging symbols (strip -g). That's the default configuration for %__os_install_post on CentOS, the step in charge on stripping binaries: $ rpmbuild --showrc (..) -14: __os_install_post %{_rpmconfigdir}/brp-compress %{_rpmconfigdir}/brp-strip %{_rpmconfigdir}/brp-strip-static-archive %{_rpmconfigdir}/brp-strip-comment-note ELF binaries are stripped with /usr/lib/rpm/brp-strip, this script explicitly calls...

hi, I noticed that RPM packages I sign use SHA1 Signature : RSA/SHA1, Fri 08 Jan 2016 10:50:58 AM PST, Key ID ad3b591d147abf59 Signatures from CentOS 7 use SHA256 Signature : RSA/SHA256, Wed 06 Jan 2016 08:54:58 AM PST, Key ID 24c6a8a7f4a80eb5 I'm trying to find where / how to use sha256 when I sign packages but I am not having much luck. Closest I have found is this :