Summary: | xattr pax-marking is erased when installing binary package | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Nikoli <nikoli> |
Component: | Binary packages support | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alexander, dev-portage, hardened |
Priority: | Normal | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 427888, 484436 |
Description
Nikoli
2013-12-27 07:28:00 UTC
(In reply to Nikoli from comment #0) > Is bug #382067 really fixed? May be portage doesn't pass --xattr option to tar? This command returns nothing (portage-2.2.7): $ qlist sys-apps/portage | xargs grep -l -- '--xattrs' (In reply to Alexander Tsoy from comment #1) > (In reply to Nikoli from comment #0) > > Is bug #382067 really fixed? > > May be portage doesn't pass --xattr option to tar? > > This command returns nothing (portage-2.2.7): > $ qlist sys-apps/portage | xargs grep -l -- '--xattrs' That's correct and that is the cause of this bug. We do have xattr support in tar, but portage isn't supplying it. Bug #382067 is fixed. Bug #465000 is almost fixed --- we have a python wrapper in there but it is too slow. This needs to be rewritten in C. But this is new. Fix: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commitdiff;h=0331526698e485508a1040d24acca5f5eff1c3f3 xattr patch for tar-1.26 is broken, so >=tar-1.27 needs to be used. Released in portage-2.2.8 |