Bug 1823866

Summary:	Flood of "/usr/bin/tar: Ignoring unknown extended header keyword 'SCHILY.dev'" messages
Product:	[Fedora] Fedora	Reporter:	Jaroslav Škarvada <jskarvad>
Component:	tar	Assignee:	Pavel Raiskup <praiskup>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	kdudka, odubaj, ovasik, pkubat, praiskup
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-24 18:24:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jaroslav Škarvada 2020-04-14 16:28:27 UTC

Description of problem:
When extracting tar archives which were probably created on the Mac OS (probably with the BSD Tar) the stderr output is flooded with strange messages. Would be possible to suppress them in the default verbosity level or write them just once? They seems harmless and just pollute stderr.

Version-Release number of selected component (if applicable):
tar-1.32-1.fc30.x86_64

How reproducible:
Always 

Steps to Reproduce:
1. wget 'https://sourceforge.net/projects/drm/files/dream/2.2/dream_2.2.orig.tar.gz'
2. tar -xzf ./dream_2.2.orig.tar.gz
3.

Actual results:
Flood of:
/usr/bin/tar: Ignoring unknown extended header keyword 'SCHILY.dev'
/usr/bin/tar: Ignoring unknown extended header keyword 'SCHILY.ino'
/usr/bin/tar: Ignoring unknown extended header keyword 'SCHILY.nlink'
/usr/bin/tar: Ignoring unknown extended header keyword 'SCHILY.dev'
/usr/bin/tar: Ignoring unknown extended header keyword 'SCHILY.ino'
/usr/bin/tar: Ignoring unknown extended header keyword 'SCHILY.nlink'
....

Expected results:
No error message in the default verbosity level or more legible error message or the error message printed just once.

Additional info:
Also reproduced on rawhide.

Comment 1 Pavel Raiskup 2020-04-15 05:31:11 UTC

Try `tar --warning=no-unknown-keyword`.  I agree that - since the
error message doesn't contain filename - we could print each message
only once.  But this needs to be discussed upstream first:
https://www.mail-archive.com/bug-tar@gnu.org/msg05848.html

Comment 2 Ben Cotton 2020-04-30 20:14:02 UTC

This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 EOL if it remains open with a
Fedora 'version' of '30'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 3 Jaroslav Škarvada 2020-05-04 08:07:57 UTC

Moving to 31.

Comment 4 Ben Cotton 2020-11-03 16:36:16 UTC

This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 EOL if it remains open with a
Fedora 'version' of '31'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 5 Ben Cotton 2020-11-24 18:24:55 UTC

Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.