Red Hat Bugzilla – Bug 496245
weird errors on generating of deltas
Last modified: 2014-03-16 23:18:26 EDT
Description of problem:
When attempting to build rawhide, I'm getting errors like:
Error genDeltaRPM for kernel-debuginfo: exitcode was 256 - Reported Error: mkdiff: could not
Error genDeltaRPM for kernel-PAEdebug-debuginfo: exitcode was 256 - Reported Error: mkdiff: could not create data
Error genDeltaRPM for gcdmaster: exitcode was 256 - Reported Error: bad cpio archive
Error genDeltaRPM for mash: exitcode was 256 - Reported Error: bad cpio archive
This is diffing:
against their prior F11 versions.
Version-Release number of selected component (if applicable):
Ok, the two different errors should mean two completely different things:
mkdiff: could not create data - deltarpm couldn't allocate enough RAM
bad cpio archive - one or both of the RPMS are corrupt
I did just test makedeltarpm mash-0.5.0-1.fc11.noarch.rpm mash-0.5.1-1.fc11.noarch.rpm temp.drpm and it worked fine. Do you mind running rpm --checksig on both mash rpms to make sure they are not corrupt?
rpm --checksig works OK.
Could you please do a manual "makedeltarpm mash-0.5.0-1.fc11.noarch.rpm
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Have you run into this any more? Do we think this was the memory problem that we're dealing with in #496242?
Yes, it continues to pop up intermittently. None in today's rawhide, but 30 in one from last week.
I don't *think* it's memory related, but I am not sure. There are no OOM messages in the logs.
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
This appears to not be showing up recently.
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.