Deprecation of $(ARCH)-geomirror.debian.net

2013.04.30 21:04 by Leo Antunes - 8 Comments

[UPDATE 2013-05-18: with Raphael Geissert’s help, all users should be now – or as soon as DNS entries propagate – be using http.debian.net without need for any change]

After the announcement of http.debian.net some months back I imagined the few people using my older $(ARCH)-geomirror.debian.net DNS redirector would relatively quickly jump ship to the newer solution, it being superior in basically every aspect. However it seems I had highly underrated the usage of my little hack. According to the server logs there still are a sensible number of genuine-looking queries being made (around 600 unique IPs in the last 3 days), and even if a sizable fraction of them are being generated by bots, this still leaves a pretty big number of potential users out there.

So I guess it’s only common courtesy to let these potential users know in a slightly more public place that I plan on pulling the plug till the end of the year. If you’re one of the people making use of the service, please migrate to http.debian.net.

Note however that this has nothing to do with cdn.debian.net, besides being based on a similar idea.

  1. I think we need to enhance the apt spec for mirrors to require looking for a NOTICE file or similar at the top of a mirror’s debian directory, and showing it on the terminal at `apt-get update` time. That would help solve problems like these.

    Reply

  2. Wouldn’t making $(ARCH)-geomirror.debian.net a DNS CNAME for http.debian.net keep things working for all your users without the need for you to keep your service online?

    Reply

    I believe it should work, but http.debian.net is a vhost, so I’d have to ask Raphael to add ServerAlias (or equivalent) entries. Certainly not the end of the world, but I originally thought it wouldn’t be worth the hassle. It’s a good point though, and I guess I should just ask Raphael…

    Reply

  3. FWIW — so you know where some of the hits come from. We configure NeuroDebian virtual appliance http://neuro.debian.net/vm.html to use $(ARCH)-geomirror. And there might be quite a few existing “installations” — so even if new ones would migrate — all other existing users would be left behind. So I would be really thankful if one or another $(ARCH)-geomirror.d.n remains available

    Reply

    Thanks for the heads-up!
    I had no idea this was going on. In this case it would indeed make sense to try and keep this online a bit longer, possibly taking Thijs’ suggestion above.
    Have you been using it for a long time? Is the current NeuroDebian release also affected?

    Reply

  4. well — we do not have “NeuroDebian release”s — trying to get everything into Debian + only a repository on top. But as for VMs — yes, current one is affected. Now that we know that this one gets deprecated (sorry — we missed original notice), we will look into switching. whenever wheezy gets released, we will push out updated one so will be off the hook there.
    May be we should also look into crafting a little postinst script for one of our packages to suggest users a substitution away from geomirror

    Reply

    Hey, you may be glad to know Raphael has agreed to your idea and the new DNS entries should be currently propagating. So your users shouldn’t have any problems!

    Reply

  5. Hi Leo — thanks! Meanwhile we adjusted our VM bootstrapping so the new wheezy VMs we rolled out already use http.d.n ;-) We thought about adding some maintainers script magic for neurodebian package to adjust those existing entries but agreed that it would be better just to announce users (and provide 1 liner) to switch to http.d.n on existing systems — that one yet TODO ;)

    Reply