FS#51708 - [milkytracker] upstream site URL leads to domain configuration page
Attached to Project:
Community Packages
Opened by the second derivative (deltasquared) - Saturday, 05 November 2016, 14:42 GMT
Last edited by Alexander F. Rødseth (xyproto) - Sunday, 27 November 2016, 18:03 GMT
Opened by the second derivative (deltasquared) - Saturday, 05 November 2016, 14:42 GMT
Last edited by Alexander F. Rødseth (xyproto) - Sunday, 27 November 2016, 18:03 GMT
|
Details
Description:
The main site for milkytracker appears to have been sold or expired; it no longer displays the main page for milkytracker but instead displays a message from joker.com, apparently a DNS registar. It is not apparent where if anywhere the site has been moved; there appears to be a github project at https://github.com/Deltafire/MilkyTracker but I have not yet attempted to contact the owner this way. Additional info: + This is agnostic of the version used as the www.milkytracker.org address is used in both the PKGBUILD and the upstream URL in the package info. Steps to reproduce: + Open URL to milkytracker.org or www.milkytracker.org via link in PKGBUILD file or pacman -Qi URL What was expected to happen: Main page for milkytracker shows up. I would post a web.archive.org link to show it's original content but said site was not co-operating at the time. Google's cache similarly did not work for any page other than the root domain, which had already changed to the joker.com message page. What actually happens: A page appears reporting to be from joker.com, a DNS registration service, stating that the URL needs configuration. This may infer change of ownership of the domain. |
This task depends upon
Closed by Alexander F. Rødseth (xyproto)
Sunday, 27 November 2016, 18:03 GMT
Reason for closing: Fixed
Additional comments about closing: The updated package will appear in [community] shortly.
Sunday, 27 November 2016, 18:03 GMT
Reason for closing: Fixed
Additional comments about closing: The updated package will appear in [community] shortly.
It also seems that a redirect to the new page has been put in place at the old address, so the existing URL now works again (So I guess it's not a bug any more).
I personally think it'd be better to change the package information to point at the new domain (the one that is redirected to), but that's a decision for the maintainer I guess.