Bug 431870 - cannot handle file with spaces in path correctly
Summary: cannot handle file with spaces in path correctly
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: quilt
Version: el5
Hardware: All
OS: All
low
medium
Target Milestone: ---
Assignee: Josh Boyer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: ActualBug
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-07 15:15 UTC by Klaus Ethgen
Modified: 2017-04-06 10:29 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-04-06 10:29:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Klaus Ethgen 2008-02-07 15:15:30 UTC
Description of problem:
Having a source where the "developer" has spaces in dirs or files quilt will
silently fail adding or removing files.

Version-Release number of selected component (if applicable):
All, upstream known (#19477)

How reproducible:
Create a file with spaces in the name and try to edit them.

Actual results:
You can edit the file without problems but it will not be in the patch if you
use quilt refresh.

Expected results:
Expected is the expected result. Sorry, but this is really what is expected.

Additional info:
I identified the problem in 3 files. /usr/share/quilt/{add,push,remove}. The
problem has to be diverted in two subproblems.
1. Using "$@" instead of "$*" or even $*.
2. Correctly quoting of the file name in the subcalls in that files.

Comment 1 Fedora End Of Life 2017-04-06 10:29:37 UTC
Fedora EPEL 5 changed to end-of-life (EOL) status on 2017-03-31. Fedora EPEL 5
is no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora
or Fedora EPEL, please feel free to reopen this bug against that version. If
you are unable to reopen this bug, please file a new report against the current
release. If you experience problems, please add a comment to this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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