search for: rpmmacro

...eference somewhere on RPM package signing that I >>>> haven't stumbled upon yet? >>>> >>>> SHA1 is broken. I shouldn't be using it. >>>> >>>> CentOS 7 is all I build packages for. >>>> >>> >>> In your .rpmmacros file .. try setting: >>> >>> _binary_filedigest_algorithm SHA256 >>> >>> or from the command line: >>> >>> rpm --define '_binary_filedigest_algorithm SHA256' <current_line> >>> >>> ===== >>> >>>...

...things change a lot. >> >> Is there an up to date reference somewhere on RPM package signing that I >> haven't stumbled upon yet? >> >> SHA1 is broken. I shouldn't be using it. >> >> CentOS 7 is all I build packages for. >> > > In your .rpmmacros file .. try setting: > > _binary_filedigest_algorithm SHA256 > > or from the command line: > > rpm --define '_binary_filedigest_algorithm SHA256' <current_line> > > ===== > > if some some reason it does not like the SAH256 value .. try 8 instead. S...

...ackages on CentOS-5 from the beginning and unless you take steps to > remove them, you will get both architectures for all packages. > > This behavior mimics the upstream behavior in RHEL. > > What you need to do after install if you want x86_64 only is this: > > 1. Modify .rpmmacros for root user and any user you want to see the > arch of packages with this value (in a .rpmmacros in the user's home > directory): > > %_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch} > > 2. Do this query (after you adjust .rpmmacros per step one) to see any >...

...gt;> Is there an up to date reference somewhere on RPM package signing that I >>> haven't stumbled upon yet? >>> >>> SHA1 is broken. I shouldn't be using it. >>> >>> CentOS 7 is all I build packages for. >>> >> >> In your .rpmmacros file .. try setting: >> >> _binary_filedigest_algorithm SHA256 >> >> or from the command line: >> >> rpm --define '_binary_filedigest_algorithm SHA256' <current_line> >> >> ===== >> >> if some some reason it does not like th...

...e signing that I >>>>> haven't stumbled upon yet? >>>>> >>>>> SHA1 is broken. I shouldn't be using it. >>>>> >>>>> CentOS 7 is all I build packages for. >>>>> >>>> >>>> In your .rpmmacros file .. try setting: >>>> >>>> _binary_filedigest_algorithm SHA256 >>>> >>>> or from the command line: >>>> >>>> rpm --define '_binary_filedigest_algorithm SHA256' <current_line> >>>> >>>>...

...gt; rpmbuild to use an alternative temporary file location? > > Try to change %_tmppath in /usr/lib/rpm/macros or build in mock and place the whole chroot on a larger drive (/etc/mock/site-defaults.cfg). and if you do not need the debug packages, add %_enable_debug_packages 0 into your .rpmmacros file -- LF

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 :

...;>> haven't stumbled upon yet? >>>>>> >>>>>> SHA1 is broken. I shouldn't be using it. >>>>>> >>>>>> CentOS 7 is all I build packages for. >>>>>> >>>>> >>>>> In your .rpmmacros file .. try setting: >>>>> >>>>> _binary_filedigest_algorithm SHA256 >>>>> >>>>> or from the command line: >>>>> >>>>> rpm --define '_binary_filedigest_algorithm SHA256' <current_line> >>&...

RPMS's rebuilt or upstream one's used Hi I got a cleanly reinstalled 4.2 workstation. However i still needed to build the following SRPMS from Mandriva/Fedora :- - Chkrootkit - Logcheck - Tripwire - Xboard & Gnuchess - Rkhunter I needed to use the upstream versions of :- - OpenOffice.org 2.0.1 - RealPlayer Gold - Acrobat Reader I needed to tweak Bind chroot to log queries and

...ry format, looks the same ... like this: pkg_name pkg_name ---------------------------- example: [root at x86-64 ~]# rpm -qa | grep popt popt-1.9.1-21 popt-1.9.1-21 ---------------------------- To fix this problem on multi-lib machines (and change the default query format), you can change your .rpmmacros (or create a .rpmmacros) in your user home directory and add this line: %_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch} --------------------------- Now the result of the above example is: [root at x86-64 ~]# rpm -qa | grep popt popt-1.9.1-21.x86_64 popt-1.9.1-21.i386 ----------------...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Centos, Is 4:perl-5.8.8-43.el5_11.x86_64 really dependent on the 32 bit perl.i386 4:5.8.8-43.el5_11 as yum is suggesting, or has something got mixed up on the system? yum install perl Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: repo.bigstepcloud.com * epel: mirror.bytemark.co.uk * extras:

...ow can I tell >>>> rpmbuild to use an alternative temporary file location? >>> >>> Try to change %_tmppath in /usr/lib/rpm/macros or build in mock and >>> place the whole chroot on a larger drive (/etc/mock/site-defaults.cfg). > > I set %_tmppath (in ~/.rpmmacros) and $TMPPATH (xz called by > find-debuginfo.sh uses it) and more parts of the build process used my > custom tmppath. But dwz still uses large temporary files in /tmp. > >> >> >> and if you do not need the debug packages, add >> >> %_enable_debug_packages...

...staller) installs i386 and x86_64 packages on CentOS-5 from the beginning and unless you take steps to remove them, you will get both architectures for all packages. This behavior mimics the upstream behavior in RHEL. What you need to do after install if you want x86_64 only is this: 1. Modify .rpmmacros for root user and any user you want to see the arch of packages with this value (in a .rpmmacros in the user's home directory): %_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch} 2. Do this query (after you adjust .rpmmacros per step one) to see any 32 bit packages installed: rpm -q...

...s/RebuildSRPM -> what SRPMs are, how to download them, how to install them, how to rebuild them -> link to the other page on how to set up your rpm-build environment 2) http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment -> install "rpm-build" package with yum -> set up ~/.rpmmacros -> tips on packages that are usually needed when building rpms (*-devel, gcc, make, etc.) Once those pages are done, the page on "building the kernel" may refer to that one for the generic instructions on how to set up rpm building environment. My WikiUserName is FilipeBrandenburger...

...the beginning and unless you take steps to >> remove them, you will get both architectures for all packages. >> >> This behavior mimics the upstream behavior in RHEL. >> >> What you need to do after install if you want x86_64 only is this: >> >> 1. Modify .rpmmacros for root user and any user you want to see the >> arch of packages with this value (in a .rpmmacros in the user's home >> directory): >> >> %_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch} >> >> 2. Do this query (after you adjust .rpmmacros per ste...

...build finds all these dependencies and adds them to the list of "Requires", which is not desirable in this case. My question therefore is - how can I tell rpmbuild to stop automatically creating a dependency list? The best I can come up with at the moment is to add the following to my ~/.rpmmacros (line numbers added by me): [1] %__os_install_post /usr/lib/rpm/brp-strip-comment-note [2] %__find_requires /bin/true [3] %__perl_requires /bin/true So: [1] - Stop it stripping already stripped binaries. [2] and [3] - This stops it doing the automatic dependency list creation. This seems...

During last update packets pidgin and libpurple were updated while "yum update"-ing Is it a common and normal thing that both x86_64 and i386 arch rpms are installed during update? This not the first time. -- Cheers, Alexx mailto:alexx187 at gmail.com

Hello, I was wondering what is the smallest install that anyone has managed with 4 (4.2 to be precise) ? I'm looking at a machine running as a VPN in a DMZ, so I'm going to remove/NOT INSTALL things like gcc, X, etc. I'm planning on putting this on a 1gb USB stick and booting from it. That reminds me, was there going to be a 1 CD server install image ? The other thing I noticed is

I am attempting to build from a src.rpm (knowing very little about rpm at all) and the spec file notes that the architecture should be set on the command line: > # platform defines - set one below or define the build_xxx on the command line Now. My question is this, how does one do this using rpmbuild? The syntax rpmbuild --target centos4 package.src.rpm seemingly has no effect.

...up /var/tmp leading to the error. How can I tell >>> rpmbuild to use an alternative temporary file location? >> >> Try to change %_tmppath in /usr/lib/rpm/macros or build in mock and place the whole chroot on a larger drive (/etc/mock/site-defaults.cfg). I set %_tmppath (in ~/.rpmmacros) and $TMPPATH (xz called by find-debuginfo.sh uses it) and more parts of the build process used my custom tmppath. But dwz still uses large temporary files in /tmp. > > > and if you do not need the debug packages, add > > %_enable_debug_packages 0 > > into your .rpmmacros...