Description of problem: Recent QA tests of xdelta3 https://bugs.mageia.org/show_bug.cgi?id=17713 exposed a fault in the builtin appheader test. See https://bugs.mageia.org/show_bug.cgi?id=17713 This test was added to the suite in the version tested in accord with the advisory https://www.debian.org/security/2016/dsa-3484. See also CVE-2014-9765. When the test suite is run the sequence aborts with the message: xdelta3: testing appheader...cp: cannot stat âxdelta3â: No such file or directory failed: : XD3_INTERNAL This was tried as an experiment in the user test directory: $ touch xdelta3 $ xdelta3 test ..... xdelta3: testing appheader... failed: compare files: different length: XD3_INTERNAL Another experiment where xdelta3 was replaced by C code demonstrated that the test function attempts to parse this text (but is not expecting C). xdelta3: testing appheader.../tmp/xdtest.recon2.4: line 1: delta1.c:: command not found /tmp/xdtest.recon2.4: line 5: //: Is a directory /tmp/xdtest.recon2.4: line 6: syntax error near unexpected token `(' /tmp/xdtest.recon2.4: line 6: `int main( )' failed: command exited non-zero: Unknown error 512 It appears that the test suite sets up symbolic links to certain files. /tmp/xdtest.recon2.4 would be 'xdelta3'. Version-Release number of selected component (if applicable): xdelta3-3.0.0-5.1.mga5 How reproducible: Always Steps to Reproduce: 1. Install xdelta3 2. $ xdelta3 test 3.
Assinging to all packagers collectively, because xdelta3 had no maintainer
CC: (none) => marja11Assignee: bugsquad => pkg-bugs
Hi Len :-) Thank you for having taken the needed time to report this issue! Did this bug get fixed? If so, please change its status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard. Thanks, Marja
Thanks Marja. Just ran the current version of xdelta3 on Mageia 6 to ensure that it still works then checked the test suite addressed by the current bug and found that it still fails at the same point. It is possible that this is close to the end of the tests and whatever the error is it does not seem to affect the main function of the program in any way. Which probably indicates that it is not important - not surprising that it has not been fixed yet. Switching version to Mageia 6, but I shall check it in Cauldron tomorrow. Len
Version: 5 => 6
OK, tried 'xdelta3 test' in a fresh Cauldron installation and saw exactly the same problem at the end of a long list of successful tests. xdelta3: testing force_behavior... success xdelta3: testing stdout_behavior... success xdelta3: testing no_output... success xdelta3: testing appheader...cp: cannot stat 'xdelta3': No such file or directory failed: : XD3_INTERNAL $ rpm -q xdelta3 xdelta3-3.0.11-1.mga7 Again, this may not be important because the application works as designed. Making the requested changes.
Whiteboard: (none) => MGA6TOOVersion: 6 => Cauldron
Checked this in mga6.1 with version xdelta3-3.0.0-7.mga6. The builtin testing sequence failed exactly as before at testing appheader. All other tests before that return "success".
I had this same problem, in Mageia 8. Only I had this problem when using xdelta3 on files in the wild, rather than on a test suite. Go to https://www.romhacking.net/translations/6462/ and download the patch, uncompress it, and apply it. Test it on a nonexistent file. You don't need a pirated ROM to test this since the error message is produce earlier than the file not found message. xdelta3 from Mageia: % xdelta3 -d -s a.ds /tmp/srww.xdelta a.ds xdelta3: unavailable secondary compressor: LZMA: XD3_INTERNAL The *same* version (3.0.11) compiled from source myself from xdelta.org): % /usr/local/src/xdelta*/xdelta3/xdelta3 -d -s a.ds /tmp/srww.xdelta a.ds xdelta3: file open failed: read: a.ds: No such file or directory xdelta must be compiled with LZMA enabled. Somehow Mageia didn't do this. Please compile this properly for Mageia 9.
CC: (none) => arromdee2
I misread; this is a different XD3_INTERNAL problem. It doesn't seem possible to delete comments here. I'll open a new big for the issue.
Is this bug solved with xdelta3-3.0.11-3.1.mga8 from bug 30652?
According comment 6 from bug 30652 this problem here is also solved. https://bugs.mageia.org/show_bug.cgi?id=30652#c6 Closing as FIXED.
Status: NEW => RESOLVEDResolution: (none) => FIXED
There seems to be little or no documentation on the xdelta3 test function. It takes no other arguments and from previous experiments appears to be looking for the program binary so in the recent bug 30652 I tried running the test against a copy of the binary and that succeeded. It may operate some kind of internal consistency check - no way of knowing. The implication is that bug 17853 is not valid.
The xdelta project is unmaintained since 5 years. This problem was already reported in 2016 upstream: https://github.com/jmacd/xdelta/issues/220 Unmaintained, undocumented, broken and 113 open issues in the bugtracker. As we can't fix code for unmaintained projects....changing to WONTFIX.
Resolution: FIXED => WONTFIX