Opened 7 years ago
Closed 7 years ago
#55576 closed defect (invalid)
qemu @2.10.1: file not found downloading distfiles
Reported by: | khepler | Owned by: | raimue (Rainer Müller) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.4.2 |
Keywords: | Cc: | ||
Port: | qemu |
Description
Qemu strangely decided to name bzip2 files with the extension ".bz2". Since Macports looks for the more traditional .bzip2 extension, the distfiles fail to download with HTTP 404 errors.
Suggest using Qemu's xz archives instead.
Change History (3)
comment:1 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | raimue@… removed |
---|---|
Owner: | set to raimue |
Status: | new → assigned |
comment:2 Changed 7 years ago by khepler
You are of course correct; I encountered the issue on Leopard/PPC. I am bewildered how I missed both the SSL error and the correct file extension considering I remember copy/pasting the URL+filename specifically from the www.qemu.org/download line -- a line that clearly reads https and is immediatey followed by the SSL error. Frankly, the implications regarding my memory are quite disturbing, compounded by my more than ten years of apparent misuse of bzip2.
In any case, this ticket isn't valid and should probably be closed. Sorry for my confusion.
comment:3 Changed 7 years ago by mf2k (Frank Schima)
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
Replying to khepler:
That's not correct. .bz2 is the normal extension for bzip2 files. Fetching this port works fine for me.
We had not mirrored the file on our servers, because of #53347. I've manually mirrored the file now and it should show up in an hour if you want to try again then.
A possible reason why the port failed to fetch for you is that you may be on an older OS version whose openssl is too old to be able to connect to qemu's https download location.
Because xz files are smaller than bz2 files, yes, the port should switch to using xz files. Perhaps this can be done when the port is updated to the next version. I see that 2.11.0 is already available from the developers.