<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.12.1"> </HEAD> <BODY> On Sat, 2007-11-08 at 18:46 -0700, NoOp wrote: <BLOCKQUOTE TYPE=CITE> <PRE> > I updated from a local mirror of the whole ubuntu archive, not from > disk. That cut out the middle-man step. ;) </PRE> </BLOCKQUOTE> <PRE> </PRE> <BLOCKQUOTE TYPE=CITE> <PRE> And that last was probably how _you_ added it. The standard update method (<A HREF="http://www.ubuntu.com/getubuntu/upgrading">http://www.ubuntu.com/getubuntu/upgrading</A>) cannot add ferm. I doubt that even the manual method (<A HREF="https://help.ubuntu.com/community/FeistyUpgradesManual">https://help.ubuntu.com/community/FeistyUpgradesManual</A>) would do this either. Neither of those use the universe repository (<A HREF="http://www.ubuntu.com/community/ubuntustory/components">http://www.ubuntu.com/community/ubuntustory/components</A>). </PRE> </BLOCKQUOTE> Sorry, but I respectfully disagree. Here was the procedure I followed in its entirety: <OL TYPE=1> <LI TYPE=1 VALUE=1>rsync the entire repo. <LI TYPE=1 VALUE=2>Use "copy:///path/to/local/repo blah blah blah" in sources.list. <LI TYPE=1 VALUE=3>Run System -> Administration -> Update Manager <LI TYPE=1 VALUE=4>Click on "Check" (to bring in the new lists of everything) <LI TYPE=1 VALUE=5>Click on the button to upgrade to 7.04 </OL> Not once did I even *LOOK* at package names (except when the errors for wxwidgets 2.6 showed up). I just waited the minute or so it took to copy the files from the local repo and waited the 1.5 hours or so it took to install everything. Then I went into Synaptic and undid the damage done to wxwidgets (and upgraded that to 2.8 which didn't cause any problems). Ferm appeared *NOWHERE* in the process. It didn't appear in any of the upgrade notices. It was nowhere near wxwidgets in Synaptic (so zero chance of having accidentally clicked on it to install). And it was not installed in Edgy: <BLOCKQUOTE> <TT>michael@tristan:/mnt/backup/edgy/07-08-11_10:35:10/etc$ sudo find . -name "*ferm*"</TT> <TT>Password:</TT> <TT>michael@tristan:/mnt/backup/edgy/07-08-11_10:35:10/etc$ cd /etc</TT> <TT>michael@tristan:/etc$ sudo find . -name "*ferm*"</TT> <TT>./default/ferm</TT> <TT>./init.d/ferm</TT> <TT>./rc2.d/S20ferm</TT> <TT>./rc3.d/S20ferm</TT> <TT>./rc4.d/S20ferm</TT> <TT>./rc5.d/S20ferm</TT> <TT>./rc0.d/K20ferm</TT> <TT>./rc1.d/K20ferm</TT> <TT>./rc6.d/K20ferm</TT> <TT>./ferm</TT> <TT>./ferm/ferm.conf</TT> <TT>michael@tristan:/etc$ </TT> </BLOCKQUOTE> So how's this for a notion?: Instead of telling a user reporting a bug that it's "impossible", figure out why the "impossible" so very obviously happened. <TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%"> <TR> <TD> -- Michael T. Richter <<A HREF="mailto:ttmrichter@gmail.com">ttmrichter@gmail.com</A>> (GoogleTalk: ttmrichter@gmail.com) If there's one thing that computers do well, it's to make the same mistake uncountable times at inhuman speed. (Peter Coffee) </TD> </TR> </TABLE> </BODY> </HTML>