Bug 188889 - kernel spec file 2.6.16 -1.2128 breaks, if deleteme exists
Summary: kernel spec file 2.6.16 -1.2128 breaks, if deleteme exists
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-13 08:43 UTC by Thomas Steudten
Modified: 2015-01-04 22:26 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-04-18 21:48:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Thomas Steudten 2006-04-13 08:43:25 UTC
Description of problem:

start building the kernel (rpmbuild -ba --target ... kernel-2.6.spec)
the %pre stage moves the old build to deleteme and starts the remove in background. 
If you break this process, the folder deleteme and deleteme2 will still
exists and the build process stops.
There's no check, if the deleteme and deleteme2 folder exists.

# We already have a vanilla dir.
  cd kernel-%{kversion}
  if [ -d linux-%{kversion}.%{_target_cpu} ]; then
     mv linux-%{kversion}.%{_target_cpu} deleteme
     rm -rf deleteme &
  fi
  if [ -d xen ]; then
     mv xen deleteme2
     rm -rf deleteme2 &
  fi


Version-Release number of selected component (if applicable):
2.6.16 -1.2128


How reproducible:
Start build process, interrupt it, start again.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Build process stops

Expected results:
Spec file should remove the deleteme folders and continue working.

Additional info:

Comment 1 Dave Jones 2006-04-18 21:48:13 UTC
for the sake of keeping the specfile as clean as possible (this snippet of
script is already pretty ugly), I'm going to close this as a "don't do that".


Comment 2 Thomas Steudten 2006-04-20 09:57:08 UTC
You can simply add "/bin/rm -rf deleteme; mv linux-xx deletme".
This don't gives the error any more, if the deleteme folder still exists.


Note You need to log in before you can comment on or make changes to this bug.