#1: enscript patch - testing
---------------------------------------------+------------------------------
Reporter: [EMAIL PROTECTED] | Owner: somebody
Type: defect | Status: new
Priority: trivial | Milestone:
Component: component1 | Version:
Resolution: | Keywords:
---------------------------------------------+------------------------------
Comment (by [EMAIL PROTECTED]):
OK. Bruce on the first patch I got the same results as you, that is, via
cygwin I ran file on the saved attachment and got:
{{{
$ file ~/enscript-1.6.4-security-1.patch
/home/jhuntwork/enscript-1.6.4-security-1.patch: ASCII C program text,
with CRLF line terminators
}}}
On the same patch but saved on the Linux machine, I get:
{{{
$ file ~/enscript-1.6.4-security-2.patch
/home/jhuntwork/enscript-1.6.4-security-2.patch: ASCII C program text
}}}
If you could just confirm by downloading this second patch from Trac to
make sure that it doesn't have CR+LF, we could definitely rule out Trac as
the problem.
Also, you should have the privs to modify/create/append tickets now.
--
Ticket URL: <http://wiki.linuxfromscratch.org/patches/ticket/1>
Patches Trac <http://wiki.linuxfromscratch.org/patches/>
Linux From Scratch Patches
--
http://linuxfromscratch.org/mailman/listinfo/patches
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
