Bug 104398 - 2 uid/gids in the source tarballs since poppler-0.60.0
Summary: 2 uid/gids in the source tarballs since poppler-0.60.0
Status: RESOLVED FIXED
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium trivial
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-28 00:47 UTC by suzuki toshiya
Modified: 2018-01-09 00:12 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
add "--owner root:0 --group root:0" options to tar command in dist target (1.05 KB, patch)
2017-12-28 00:47 UTC, suzuki toshiya
Details | Splinter Review

Description suzuki toshiya 2017-12-28 00:47:38 UTC
Created attachment 136415 [details] [review]
add "--owner root:0 --group root:0" options to tar command in dist target

Because git-archive always uses root:root in the generated tarball,
the source tarballs (since 0.60.0) have 2 uid/gids in it.
"root:root" by git-archive, and normal users/group by normal tar.
For detail, please find the analysis at::
https://lists.freedesktop.org/archives/poppler/2017-December/012737.html

Here is a trivial patch adding "--owner root:0 --group root:0" to the
dist target of cmake.

Also I've written a patch for git-archive. If the maintainer wants
to postpone the decision after seeing how git maintainers deals with,
please do so.

Regards,
mpsuzuki
Comment 1 Albert Astals Cid 2018-01-08 23:04:31 UTC
Pushed
Comment 2 suzuki toshiya 2018-01-09 00:12:33 UTC
Thanks. I've proposed to add "--owner" like options to git,
https://public-inbox.org/git/5A4EFDAD.3050105@hiroshima-u.ac.jp/T/#t
but the response was not so positive.
An alternative solution to include untracked files to the archive was proposed.
It seems that the implementation and distribution would take some time,
so I highly appreciate the application of my temporal patch specific.

Thanks again!


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.