FS#69373 - [tar] --to-stdout extracts files to filesystem anyway

Attached to Project: Arch Linux
Opened by Gaetan Bisson (vesath) - Tuesday, 19 January 2021, 20:58 GMT
Last edited by Sébastien Luttringer (seblu) - Saturday, 13 February 2021, 13:25 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When used with the --to-stdout option tar-1.33-1 extracts files to the filesystem in addition to printing their contents to stdout. Consider for instance:

/usr/bin/tar --extract --to-stdout --file /var/lib/pacman/sync/core.db

It should only print the contents of the files in the tarball to stdout, but it now mistakenly also extracts those files to the filesystem.
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Saturday, 13 February 2021, 13:25 GMT
Reason for closing:  Fixed
Comment by Doug Newgard (Scimmia) - Wednesday, 20 January 2021, 11:56 GMT
And you think this is a packaging problem?
Comment by Gaetan Bisson (vesath) - Wednesday, 20 January 2021, 18:04 GMT
No. This is a bug tracker, not a "packaging problem" tracker.
Comment by Doug Newgard (Scimmia) - Wednesday, 20 January 2021, 18:10 GMT
https://wiki.archlinux.org/index.php/Bug_reporting_guidelines#Upstream_or_Arch?
Comment by Gaetan Bisson (vesath) - Wednesday, 20 January 2021, 18:26 GMT
So you just won't assign this bug report to the package maintainer (seblu)?
Comment by Erich Eckner (deepthought) - Thursday, 04 February 2021, 12:48 GMT
I reported it upstream (you don't even need to provide an email address, just some general knowledge about literature :-P)
https://savannah.gnu.org/bugs/index.php?60002
Comment by Sergey Poznyakoff (gray) - Thursday, 04 February 2021, 15:00 GMT
Thanks. The bug is fixed by the following commit: https://git.savannah.gnu.org/cgit/tar.git/commit/?id=ee2ec5ff190fb91841fe7989c1c0b57f0a1eadb2. I plan to release a new version within a week.
Comment by Emil (xexaxo) - Thursday, 04 February 2021, 15:21 GMT
@Scimmia I suspect something like the following may have been more fruitful:
"Sounds like an upstream bug, please report it there and add link us to the issue"
Comment by Eli Schwartz (eschwartz) - Thursday, 04 February 2021, 16:48 GMT
  • Field changed: Status (Unconfirmed → Assigned)
  • Field changed: Category (Packages: Core → Upstream Bugs)
  • Task assigned to Sébastien Luttringer (seblu)
I think it's generally considered a pretty good idea when reporting a bug to the distro, if you have a reasonable expectation that it's an upstream bug, to also report it to the correct location for actually getting it fixed!

Vesath, you *know* that we are not empowered here to fix upstream bugs, but merely to ask you to report it upstream and notify us when there is an available patch to backport.

It is true that you could also request the package maintainer to report a bug on your behalf... this is a bit inefficient though.
Comment by Sébastien Luttringer (seblu) - Friday, 05 February 2021, 10:01 GMT
@Eli, thanks for assigning me.

Well, if Sergey release a new version next week, I'll wait for it.
Comment by Sergey Poznyakoff (gray) - Saturday, 13 February 2021, 11:58 GMT
GNU tar version 1.34 is available for download. It includes the discussed fix.
Comment by Sébastien Luttringer (seblu) - Saturday, 13 February 2021, 13:25 GMT
Thanks! Package is in [testing]. It will land in [core] as soon as it gets its signoffs.

Loading...