cancelling after changing mirrors in software-properties behaves strangely

I think the reload repositories updates all the repositories and not just the newly added one.

If you suggest automatically removing the newly added repo when the reload is canceled, it would affect the following scenarios:

1. The user has a bad internet connection and reload doesn't work
2. The repository is down (but the user wants to keep it and reload repos later)

In your situation, you could always go back and remove the repo yourself using software-properties

Perhaps software-properties should not close though when you click Cancel so you have the opportunity to remove the repo. By the application just closing it is not clear which repo you will be using afterwards.

>Perhaps software-properties should not close though when you click Cancel

The reload 'pop-up' appears only after you close software-properties. If you choose to reload, the software-properties widow still stays grayed out in the background.
Maybe we should have an additional option to reload repos on the software-properties window itself.

What's the take on this bug? Is it a 'wishlist' or not valid? Let us not leave it as 'new' and 'unconfirmed' for a year(There are already 5000 of them).

I'm Won't Fixing the Hardy task since it didn't make it and is not SRU worthy but will create an Intrepid task.

Thanks for your bugreport.

Sorry that this didn't get fixed in intrepid. I'm afraid its too late now, because fixing this requires changes in synaptic and software-properties and at this point in the release that is too risky.

We should evaluate this for -updates or fix it early in jaunty IMO.

Maybe there should be a pop-up stating "Are you sure you want to continu with these repositories - [name of servers]"
When saying yes - > updates are cancelled and software-properties close
When saying no - > updates are cancelled and software-properties stay open giving the opurtunity to revert back to the former or other servers

This should give a clear message and choice.

Intrepid Ibex reached end-of-life on 30 April 2010 so I am closing the
report. The bug is still marked as confirmed in later versions of Ubuntu.

Thank you for reporting this bug to Ubuntu. Gutsy reached EOL on April 18th, 2009.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with Oneiric and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Marking as Invalid after 8 months without response or any activity, as I didn't see this on Oneiric or Quantal.