Bug 628412

Summary: fedpkg import screws up .gitignore
Product: [Fedora] Fedora Reporter: Mattias Ellert <mattias.ellert>
Component: fedora-packagerAssignee: Dennis Gilmore <dennis>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: dcantrell, dennis, mcepl, mcepl
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-30 22:04:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mattias Ellert 2010-08-29 23:57:51 UTC
Description of problem:
When I ran fedpkg import the updated .gitignore is incorrect

Version-Release number of selected component (if applicable):
fedora-packager-0.5.1.2-2.fc12.noarch

The old source file was not removed from the .gitignore file, and the new source file was added with an extra slash in front of its name.
  
Actual results:
$ cat .gitignore
root-5.26.00c.tar.gz
/root-5.26.00d.tar.gz

Expected results:
$ cat .gitignore
root-5.26.00d.tar.gz

Comment 1 Jesse Keating 2010-08-30 22:04:05 UTC
These are both by design.

Removing items from a config file that is likely to be edited outside the program is a risky business, one that I am not willing to get into right now.  Therefor we leave it in place.

Also the leading slash is part of gitignore syntax.  It says to ignore the file in the top level repo directory, but should the file show up in any lower directory do not ignore it.  This was an RFE from a user, but it came after the initial conversion and launch of fedpkg.

Comment 2 Matěj Cepl 2015-01-28 15:31:28 UTC
See followup for the bug of which this is in fact a duplicate on bug 627987

Comment 3 Matěj Cepl 2015-01-28 15:32:27 UTC

*** This bug has been marked as a duplicate of bug 627987 ***