[MacPorts] #31987: netpbm install tries to fetch nonexistent file
MacPorts
noreply at macports.org
Tue Nov 8 18:29:27 PST 2011
#31987: netpbm install tries to fetch nonexistent file
----------------------------------+-----------------------------------------
Reporter: nathmclean@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.0.3
Keywords: | Port: netpbm
----------------------------------+-----------------------------------------
Changes (by ryandesign@…):
* port: => netpbm
Old description:
> I am trying to install netpbm through macports, however it fails with the
> message:
>
> "Error: Target org.macports.fetch returned: Subversion check out failed"
>
> After inspecting the log file (attached) it seems to me the problem lies
> in that mac ports is trying to fetch the file:
> netpbm-10.47.31_0.darwin_10.x86_64.tgz
> from
> http://packages.macports.org/netpbm/
> and gets a 404 error
>
> The actual file at that location is a different type of archive, using
> the file extension tbz2.
>
> I am new to using MacPorts and I was wondering if there is any quick and
> dirty way to change the archive MacPorts looks for when I type the
> command "port install netpbm"
>
> I have just updated MacPorts definitions using "port selfupdate" so it
> seems to me that this is a bug.
>
> Thanks in advance!
New description:
I am trying to install netpbm through macports, however it fails with the
message:
{{{
Error: Target org.macports.fetch returned: Subversion check out failed
}}}
After inspecting the log file (attached) it seems to me the problem lies
in that mac ports is trying to fetch the file:
netpbm-10.47.31_0.darwin_10.x86_64.tgz
from
http://packages.macports.org/netpbm/
and gets a 404 error
The actual file at that location is a different type of archive, using the
file extension tbz2.
I am new to using MacPorts and I was wondering if there is any quick and
dirty way to change the archive MacPorts looks for when I type the command
"port install netpbm"
I have just updated MacPorts definitions using "port selfupdate" so it
seems to me that this is a bug.
Thanks in advance!
--
--
Ticket URL: <https://trac.macports.org/ticket/31987#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list