On Tue, Jan 17, 2012 at 4:48 PM, Yury V. Zaytsev <[email protected]> wrote:
> On Tue, 2012-01-17 at 22:34 +0100, David Hrbáč wrote:
>>
>> Thanks, can you file the issue on GitHub cpio errors? Are you able to
>> submit spec pull request on GitHub?
>
> I think it's just the RHEL5 / RHEL6 / sha1 / xz issue...
>
> --
> Sincerely yours,
> Yury V. Zaytsev
Oh, goddess, that... I personally deal with it by using "mock" on an
RHEL 6 box to build for RHEL 5 environments.
The quick/dirty work around is to use 'rpm2cpio' to extract the
contents of the SRPM, and build a new RHEL 5 compatible SRPM.
cd /tmp
wget foo-1.0-1.el6.src.rpm
cd ~/rpm/SOURCES # or wherever your .rpmmacros is set to do
your builds from
rpm2cpio < /tmp/foo-1.0-1.el6.src.rpm | cpio -id
mv foo.spec ../SPECS
rpmbuild -bs --nodeps ../SPECS/foo.spec
rpmbuild --reubild ../SRPMS/foo-1.0-1.el5.src.rpm
The release names will be tweaked somewhat by the '%{?dist}' value in
the .spec file.
The problem is that RPM updated a number of specifications, especially
checksum handling, between RHEL 5 and 6, and between various versions
of Fedora.
_______________________________________________
users mailing list
[email protected]
http://lists.repoforge.org/mailman/listinfo/users
