Bug 461600

Summary: Wrong exit code when freshening non-existing archive
Product: Red Hat Enterprise Linux 5 Reporter: Josef Zila <jzila>
Component: zipAssignee: Karel Klíč <kklic>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 5.2CC: rvokal
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 602718 (view as bug list) Environment:
Last Closed: 2010-04-13 15:01:09 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:
Bug Depends On:    
Bug Blocks: 602718    

Description Josef Zila 2008-09-09 11:52:48 UTC 
Description of problem:
According to http://www.info-zip.org/FAQ.html#error-codes, zip should return exit code 13 when attempting to freshen archive that does not exist, it produces correct error message, but returns exit code 12 instead

How reproducible:
zip -f archive
  
Actual results:
# zip -f archive
	zip warning: archive.zip not found or empty
# echo $?
12


Expected results:
# zip -f archive
	zip warning: archive.zip not found or empty
# echo $?
13
Comment 1 Radek Vokál 2010-04-13 15:01:09 UTC 
This has zero impact on customer, or it even might have negative impact on those relying on wrong return code (ok, I hope there are no customers like that). I'm closing this bug in RHEL5. Karel, please make sure this issue is addressed in RHEL6 and further.