Bug 122532 - quilt refresh removes header if no ~/.quiltrc present
Summary: quilt refresh removes header if no ~/.quiltrc present
Status: RESOLVED INVALID
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Development (show other bugs)
Version: unspecified
Hardware: PowerPC Linux
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Andreas Gruenbacher
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-10 18:16 UTC by Olaf Hering
Modified: 2008-07-16 15:46 UTC (History)
0 users

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

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

Note You need to log in before you can comment on or make changes to this bug.
Description Olaf Hering 2005-10-10 18:16:50 UTC 
I built quilt for sles9-ppc due to the fortify changes in 10.0.

a fresh user with no quiltrc can not do quilt header -e, a quilt refresh will
remove the changes.
There is no diffstat installed, maybe thats related.

I'm seeing this on chokeberry.
Comment 1 Olaf Hering 2005-10-10 18:18:19 UTC 
the presence of diffstat seems to make a difference.
I wonder why diffstat is not added per default.
Comment 2 Andreas Gruenbacher 2005-10-11 23:22:22 UTC 
I don't see anything obvious. Could you please send the output of ``quilt 
--trace refresh''?
Comment 3 Olaf Hering 2005-10-12 06:59:44 UTC 
the version from 10.0 works, the one from stable not. will try.
Comment 4 Olaf Hering 2005-10-14 12:48:06 UTC 
odd, I cant reproduce it today.
Comment 5 Olaf Hering 2006-01-16 14:04:19 UTC 
I just got that now on pomegranate.

sudo su - olaf
cd /dev/shm/r/linux-2.6.15
quilt header -e

quilt refresh will trash the header.
Comment 6 Andreas Gruenbacher 2006-01-16 14:10:17 UTC 
Can you please move it somewhere (on pomegranate?) where I can check this tonight/tomorrow? Thanks!
Comment 7 Andreas Gruenbacher 2006-01-17 12:03:52 UTC 
Olaf and I tried to reproduce this problem together, and we again couldn't. Maybe it'll trigger again later...