Re: etch --> testing
charlie derr wrote:
SNIP
He actually has a second machine (laptop) with ubuntu on it (an 
attempt to switch distros in the past).  Since I'm not nearly as 
proficient with untangling ubuntu problems as I am with understanding 
debian, I don't think that it really makes sense (in the past there 
were other ubuntu-lovers around that he could also lean on but that's 
no longer the case).   The laptop has dapper on it, and from what 
little I've read, the upgrade path for ubuntu mostly means 
wipe;reinstall -- if the desktop machine goes to testing without much 
of a hitch, then I guess we'll then be faced with the decision of what 
to upgrade the laptop to.
This guy has actually been running debian for a lot longer than I have 
(though always with assistance).  While it's sometimes a bit 
frustrating to always be on the hook no matter what issue he might be 
having, I do feel it's important to support the "ethos" that drives 
his insistence on using debian/GNU linux (his understanding of the 
political ramifications of using free software is something I 
obviously support completely, and it's the reason I'm willing to go 
the extra mile for him).   It's a little bit interesting to me that my 
query brought a debate as to whether ubuntu would be more appropriate 
(not a question I was asking).  I was more looking for some feedback 
from someone who might have upgraded from etch to testing recently 
about specific pitfalls.
SNIP
I just re-installed stable and dist-upgraded to unstable.  The problem I 
had was differences in the package for dpkg.  dpkg would not configure 
or install package dpkg because of dependency issues.  I had to do dpkg 
-i --force-depends-version /path/packaged/dpkg.deb
After that and two different apt-get -f install, all was well (required 
one reboot to fix HAL).
If any of this bothers you, perhaps you should stay with stable.  And 
this was a dist-upgrade to sid, I don't know if I would have found that 
issue in testing or not.
--
Damon L. Chesser
damon@damtek.com
404-271-8699
Reply to: