Projects
New Ticket     Wiki     Browse Source     Timeline     Roadmap     Bug Reports     Search

Ticket #13001 (closed defect: fixed)

Opened 13 months ago

Last modified 10 months ago

port file command returns the path to the portfile with \r at end

Reported by: ebgssth@… Owned by: ryandesign@…
Priority: Normal Milestone: MacPorts base bugs
Component: base Version: 1.5.0
Keywords: Cc: ebgssth@…, afb@…, ryandesign@…
Port:

Description

$ ls `port file libevent`
: No such file or directory/sources/rsync.macports.org/release/ports/devel/libevent/Portfile

$ port file libevent | sed -n l
/opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/libevent/Portfile\r$

This problem makes diffing Portfile harder. When I'm editing Portfile and like to do diff, I need to do something like

port cat portname > Portfile.orig
port edit portname
diff -u Portfile.orig `port file portfile | tr "\r" " "` 

Change History

Changed 13 months ago by afb@…

This problem is not present in trunk, when using the bash shell.

Changed 13 months ago by ryandesign@…

  • cc ebgssth@…, afb@…, ryandesign@… added
  • owner changed from macports-dev@… to ryandesign@…
  • milestone set to MacPorts base bugs

Changed 13 months ago by ryandesign@…

  • status changed from new to closed
  • resolution set to fixed

Agree, I cannot reproduce this on MacPorts trunk.

Changed 13 months ago by ryandesign@…

  • summary changed from port file comamnd returns the path to the portfile with ¥r to port file command returns the path to the portfile with \r at end

Changed 13 months ago by ebgssth@…

  • status changed from closed to reopened
  • resolution fixed deleted

This problem seems to only occur in OS X 10.3. On 10.4 I cannot reproduce this, too.

Changed 13 months ago by afb@…

Can't reproduce this on Mac OS X 10.3 with MacPorts 1.5.0 either.

I think your install is broken ?

Changed 13 months ago by ebgssth@…

I'm using 1.520 on Mac OS X 10.3.9, just re-installed MacPorts.

Changed 13 months ago by ebgssth@…

Re-installed OS X 10.3 and MacPorts 1.520 but this bug still remains.

Changed 10 months ago by ebgssth@…

verified this problem was fixed in macports 1.600. Please close this ticket.

Changed 10 months ago by ryandesign@…

  • status changed from reopened to closed
  • resolution set to fixed
Note: See TracTickets for help on using tickets.