Summary: | sys-devel/patch-2.7[xattr] applying patches warns when fs doesn't support xattrs | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ben Kohler <bkohler> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bkohler, staff |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
"strace patch -p0 < test.patch" output log
"emerge =portage-2.2.0_alpha128" failure |
Description
Ben Kohler
2012-09-18 06:01:38 UTC
do you have xattr support enabled in your kernel for those filesystems ? please attach your kernel .config. Commit message: Add USE=xattr flag http://sources.gentoo.org/sys-devel/patch/patch-2.7.ebuild?r1=1.1&r2=1.2 It only fails when extended attributes are disabled on the FS driver. I have actually only tested that bit on ext2 so far but I assume it's the same on others. Created attachment 324300 [details]
"emerge =portage-2.2.0_alpha128" failure
This xattr USE flag helps, but just to be clear-- if USE=xattr is still enabled but the FS on /var/tmp/portage (or wherever patch is writing its result) does not support xattr, it is fatal. Patch errors out and emerge errors out.
If doing a basic patch test from CLI, the patch result is never written to the filesystem.
can you try this snapshot: ftp://alpha.gnu.org/gnu/patch/patch-2.7.0.21-89e5.tar.gz it should have this bug fixed Yes this snapshot works perfectly should be all set now in the tree; thanks for the report! Commit message: Version bump http://sources.gentoo.org/sys-devel/patch/patch-2.7.1.ebuild?rev=1.1 |