This just caused a regression from my perspective, because we had tools that were working against Precise and just broke because the armadaxp netboot images just vanished (from the perspective of the script).
I notice that the server install instructions have already been updated to link to the new location, so perhaps this is not so bad on this occasion. The amount of tooling around armadaxp is currently fairly limited, so it is probably better overall to have Precise's netboot location consistent since it won't be too hard to update things. But in future, other automated tools (eg. MAAS) will expect to find the netboot images at the same location that they were at release time. Please consider these (and tools used by users that we can't necessarily update) before moving netinst image URLs after release in future. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010708 Title: create armadaxp netboot directory and move files into it To manage notifications about this bug go to: https://bugs.launchpad.net/eilt/+bug/1010708/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
