<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title><![CDATA[Update rollback functionality]]></title>
    <link>http://brainstorm.ubuntu.com/item/9625/</link>
    <description><![CDATA[Imagine I work in a corporate environment, I install some updates, and suddenly things stop working.<br /><br />People cant access their e-mail, or shared files on the network, or perhaps have no internet connectivity.<br /><br />I am about to crap my pants.<br /><br />The business workflow stops, people are getting impatient and the boss is hugely disappointed. Now everyone wants to hang me by the balls.<br /><br />I cant tell them "Just wait a couple of hours, I'll google a solution".<br /><br />Now, wouldn't it be great with a rollback feature?<br />$ sudo apt-get rollback samba<br />Or something, and a second later, everything is back to normal, everyone is happy and my balls are safe.<br />
<br />


<b>[235 votes] Solution #1: Auto-generated solution of idea #9625</b>
<br />

<br />
<br />



<b>[3 votes] Solution #2: Updates should be version numbered, so that user can update to specific version</b>
<br />

<br />
<br />



<b>[3 votes] Solution #3: Have an easy way to store big groups of packages for reinstalling</b>
<br />

<br />
<br />



]]></description>

    <language>en-us</language>
    <pubDate>Sat, 07 Jun 2008 14:43:27 +0000</pubDate>
    <lastBuildDate>Thu, 21 May 2009 17:28:58 +0000</lastBuildDate>
    <generator>QAPoll module</generator>
    <guid isPermaLink="true">http://brainstorm.ubuntu.com/idea/9625/</guid>
        <item>
  <title>Comment from Auzy</title>
  <description><![CDATA[Actually, wouldn't it be better to track all changes made to apt? So that you can rollback to any previous revision? Might make more sense to do that via Timevault though (otherwise config files may crash and burn)<br /><br /><br />Either way, +1, its a good idea]]></description>
  <pubDate>Sat, 07 Jun 2008 15:16:31 +0000</pubDate>
</item>
        <item>
  <title>Comment from Eldmannen</title>
  <description><![CDATA[Auzy,<br />Yeah, that would be nice too.<br />You select a date and see all updates installed that day.]]></description>
  <pubDate>Sat, 07 Jun 2008 20:38:56 +0000</pubDate>
</item>
        <item>
  <title>Comment from jhoger</title>
  <description><![CDATA[My new favorite out-of-context quote<br /><br />"I am about to c**p my pants." -- Eldamannen of Brainstorm<br /><br />Anyway I think Auzy is right... if for some reason a squishy-panted admin^H^H^H^H^Hcomputer guy is willing to just let every package update on his production server without testing the changes, the thing that will help this misguided soul the most is being able to rollback everything to just prior to the update, since most likely such a computer guy probably has no idea what broke anyway.<br /><br />Aside from the colorful language, I'm pretty sure this idea is a dump^H^H^H^Hdupe though.]]></description>
  <pubDate>Sun, 08 Jun 2008 05:53:23 +0000</pubDate>
</item>
        <item>
  <title>Comment from DanRabbit</title>
  <description><![CDATA[voted up for "now everyone wants to hang me by my balls"]]></description>
  <pubDate>Sun, 08 Jun 2008 14:56:20 +0000</pubDate>
</item>
        <item>
  <title>Comment from booksbuggy</title>
  <description><![CDATA[My computer has experienced this kind of situation a lot.]]></description>
  <pubDate>Sat, 27 Sep 2008 15:35:59 +0000</pubDate>
</item>
        <item>
  <title>Comment from phoenix</title>
  <description><![CDATA[I experienced this with Jaunty recently.  Installed a fresh system and when I installed the recommended updates, the notification system for the volume control went haywire, generating 100s of notifications in a second.  CPU utilization was 100%.<br /><br />My only option was to format the system and no run update-manager.  I was lucky because this was a freshly installed system.  What if it was a 6 month old system and suddenly the updated packages hosed the system?<br /><br />The system should automatically set a checkpoint before upgrading itself, and provide a simple facility to rollback from the last update.]]></description>
  <pubDate>Thu, 21 May 2009 10:49:29 +0000</pubDate>
</item>
        <item>
  <title>Comment from AndrewLuecke</title>
  <description><![CDATA[Btw, rolling back isn't always that simple, because config files may have been updated.. Thats why we need full revision control on everything. ]]></description>
  <pubDate>Thu, 21 May 2009 17:28:58 +0000</pubDate>
</item>
      </channel>
</rss>
