Bug 704561
Summary: | applydeltaiso fails | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John Reiser <jreiser> |
Component: | deltarpm | Assignee: | Jonathan Dieter <jonathan> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 14 | CC: | jonathan |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-08-16 21:27:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
John Reiser
2011-05-13 15:34:05 UTC
Works with deltaiso-3.6-0.6.20110223git.fc15.x86_64 The problem is that deltarpm in F14 is linked against xz-4.999.9, while in F15 it's linked against xz-5.0.1. In the switchover from 4.999 to 5.0, xz modified its compression algorithm so that compressed files are (very) slightly different. If you're interested, see http://cedarandthistle.wordpress.com/2011/02/16/brittle-deltas-a-possible-solution for more detail. So, basically, we're stuck. If you apply a F15 deltaiso using deltaiso from F15, it works (as you've already seen). If you use the F14 one, it won't. One thought Andre Robatino and I were throwing around was to host a F14 copy of deltaiso that was statically linked against xz-5.0.x so you could use it for F15 deltaisos, but then that version of deltaiso will no longer work with F14 deltaisos. Anyhow, there's no easy way that I can see to fix this. Afraid I'm going to have to close this as CANTFIX. If you can see a workable solution, please reopen. Please comment on these two possibilities which have slightly different goals. 1) Goal: generate intended output (byte-for-byte identical). Method: add a commandline parameter "--external-xz='<path_and_paramters>'" which lets the user specify a substitute xz and its command-line flags. Then the expert user could use the other xz installed somewhere else, or could specify flags that would cause xz to choose its settings to be compatible with specific .isos. 2) Goal: generate "usable" output: something that will pass MediaCheck and will install correctly, but may be different from the intended .iso because of xz differences. Method: detect non-equality as now, but then recover. Run implantisomd5 on the output so that MediaCheck passes, change the exit code from 1 to 2, change the stderr message to something such as "The output is not byte-for-byte identical with the intended .iso because of differences in xz compression. However, the output .iso is equivalent: the results of an install will be the same, and the .iso also passes MediaCheck." Choice 2) will require significant work. "implantisomd5 --force" succeeds and the resulting .iso boots, passes MediaCheck, and begins an install. However, most of Packages/*.rpm is garbage; begining with: ----- error: deja-dup-18.1.1-1.fc15.i686.rpm: not an rpm package (or package manifest) error: dejavu-fonts-common-2.33-1.fc15.noarch.rpm: not an rpm package (or package manifest) error: dejavu-lgc-sans-fonts-2.33-1.fc15.noarch.rpm: not an rpm package (or package manifest) error: dejavu-lgc-sans-mono-fonts-2.33-1.fc15.noarch.rpm: not an rpm package (or package manifest) [snip] ----- as diagnosed by "rpm --verify -p Packages/*.rpm"; 2471 out of 2944 are bad. This looks like applydeltaiso has shifted the blocks of an ISO9660 filesystem without adjusting the directory entries. Applydeltaiso claims "copying unchanged" for almost every *.rpm (all except the 7 mentioned in original Description above) but it seems that the copy did not go to the correct blocks of the .iso per the ISO9660 directory. Altogether, it seems to me that applydeltaiso should adopt a more-sceptical attitude. Examine the names of the .rpms, and refuse to proceed when a known bad case is detected (such as this case, with mismatched xz for .fc15 on Fedora 14). Even more, use evidence-based tests: pick the 25th-largest .rpm, uncompress it, re-compress it, and refuse to proceed unless it matches the original. This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |