Bug 677084 - Error unpacking rpm package iputils-20101006-7.fc15.x86_64
Summary: Error unpacking rpm package iputils-20101006-7.fc15.x86_64
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: iputils
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jiri Skala
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-13 08:29 UTC by Magnus Tuominen
Modified: 2014-11-09 22:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-14 15:47:48 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Magnus Tuominen 2011-02-13 08:29:19 UTC 
Description of problem:
I am trying to build a package using mock -r fedora-rawhide-x86_64-rpmfusion_free and it fails every time with this error:

Error unpacking rpm package iputils-20101006-7.fc15.x86_64
error: unpacking of archive failed on file /bin/ping: cpio: cap_set_file failed - Operation not supported
1115 blocks

Failed:
  iputils.x86_64 0:20101006-7.fc15

Version-Release number of selected component (if applicable):
iputils.x86_64 0:20101006-7.fc15

How reproducible:
Always

Steps to Reproduce:
1. Start a mockbuild for rawhide
2. Wait for yum to get the files
3. Fail when installing
  
Actual results:
Mock fails to install all needed packages and build.

Expected results:
Mock tries to build package.

Additional info:
Comment 1 Jiri Skala 2011-02-14 13:31:58 UTC 
Hi,
I've tested it and everything works fine BUT:

I suppose you ran into problems due to mass rebuild + f15 branches creation. You should also verify your mock configs. Let me know about your's findings.

Jiri
Comment 2 Magnus Tuominen 2011-02-14 15:41:32 UTC 
Seems to be fixed now after disabling tmpfs_* in my /etc/mock/site-defaults.
Comment 3 Jiri Skala 2011-02-14 15:47:48 UTC 
ok, thanks for feedback - closing 'not a bug'
Note You need to log in before you can comment on or make changes to this bug.