Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vmalloc and vcodex downloads are failing #749

Closed
apjanke opened this issue May 1, 2016 · 10 comments
Closed

vmalloc and vcodex downloads are failing #749

apjanke opened this issue May 1, 2016 · 10 comments
Labels
upstream issue An upstream issue report is needed

Comments

@apjanke
Copy link
Contributor

apjanke commented May 1, 2016

The vmalloc download is failing due to a redirect loop or something similar. Affects both the tarball itself and that ~astopen user home page.

$ brew install -s vmalloc
==> Using the sandbox
==> Downloading http://www2.research.att.com/~astopen/download/tgz/vmalloc.2013-05-31.tgz
==> Downloading from http://www.research.att.com/~astopen/download/tgz/vmalloc.2013-05-31.tgz
######################################################################## 100.0%
curl: (47) Maximum (50) redirects followed
Error: Failed to download resource "vmalloc"
Download failed: http://www.research.att.com/~astopen/download/tgz/vmalloc.2013-05-31.tgz

I emailed their webmaster using the contact info at the bottom of the www.research.att.com site.

Archive.org's wayback machine does not have this archived.

Also affects vcodex, which is hosted on the same site.

Also affects ksh, which was hosted on the same site. But it has a third-party mirror that we have switched to, so it's still working.

@apjanke apjanke mentioned this issue May 1, 2016
53 tasks
@apjanke apjanke changed the title vmalloc download is failing vmalloc and vcodex downloads are failing May 1, 2016
@ilovezfs
Copy link
Contributor

ilovezfs commented May 1, 2016

@apjanke I suspect this is deliberate since it coincides with the appearance of the GitHub repo.

@apjanke
Copy link
Contributor Author

apjanke commented May 1, 2016

Probably so (though I bet they meant to redirect to a new landing page instead of creating a broken redirect loop). I saw you mention this on the other issue and ask them for a tagged release (att/ast#3). Hopefully they'll do so.

But it's been like two months since you asked about a tag, and no response. Seems like this project may be moribund, or at least not making formal releases available. If that's the case, it's probably boneyard time for both of vmalloc and vcodex, since they don't meet Homebrew acceptance criteria any more.

@ilovezfs
Copy link
Contributor

ilovezfs commented May 1, 2016

That may mean ksh has to go too since it's living on third-party link life support. :(

@apjanke
Copy link
Contributor Author

apjanke commented May 1, 2016

That'd be a bummer. Ksh is not exactly obscure software.

The Download link from http://www.kornshell.com/ is a link to http://www.research.att.com/sw/download, which is also a broken redirect loop. They should be notified too. Does someone want to, uh, email David Korn and ask him where to find releases now?

@apjanke
Copy link
Contributor Author

apjanke commented May 1, 2016

Okay. I emailed email. We'll see if they can help us.

@apjanke apjanke added the upstream issue An upstream issue report is needed label May 1, 2016
@apjanke
Copy link
Contributor Author

apjanke commented May 2, 2016

I emailed AT&T research, and they confirmed that it has been moved to that GitHub repo. I asked about labeling releases via email too; we'll see what they have to say there. I heard back on email within a day, so they might be more responsive there than on their GitHub issue tracker.

@ilovezfs
Copy link
Contributor

ilovezfs commented May 2, 2016

Excellent news!

I'm wondering if we're going to want a new single monolithic ast formula, since there seems to be a new build system all in one repo, or if it'll be better to keep the formulae separated, and use the same underlying repository for all of them, with the specific package selected per formula.

@DomT4
Copy link
Member

DomT4 commented May 22, 2016

Any update on this?

@ilovezfs
Copy link
Contributor

@MikeMcQuaid
Copy link
Member

Closing out upstream issues.

@Homebrew Homebrew locked and limited conversation to collaborators May 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
upstream issue An upstream issue report is needed
Projects
None yet
Development

No branches or pull requests

4 participants