LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices

Reply
 
Search this Thread
Old 05-11-2004, 09:36 PM   #1
xanas3712
Member
 
Registered: Apr 2004
Distribution: Slackware/Mandrake/Debian (sarge)
Posts: 266

Rep: Reputation: 30
Proper method to upgrade debian system?


Ok.. I didn't get much of an answer earlier beyond a basic faq which was extremely long and didn't explain what I was looking for.

What I want is specific commands I need to update a debian based system to the sarge packet-set that should not generate errors.

So far everytime I've done this it's been an absolute disaster and it's beginning to make me think debian is worse than any other distro...

Here is what I've been doing.. and I'm going to be as specific as I want whoever responds to be so please don't send me generalized stuff.

Install (first woody now libranet)... now the first part here may be what's going wrong. Both of these distros pretty much force me to have one of the stupid x login managers. I figured out how to remove them, but after I started upgrading.. so perhaps that maybe part of the problem. That I'm trying to upgrade with x running. Not that I can do much about it when telinit 3 to runlevel 3 won't get me out of x and into a base console (now note.. I do know how to do this now but not before.. though I still find it a pretty lame solution)..

So.. while in KDE I've been doing the following. Bring up a console.. su to root.. then edit /etc/apt/sources.list and set the dist to sarge instead of woody
then save file
command...
apt-get dist-upgrade
downloads...... all the packages
then starts asking some basic configuration questions
I continue.. then it starts unpacking and setting up
and then the problems come.. dpkg gives errors and it stops.. I try apt-get -f dist-upgrade.. no go..

Anyway.. what else do I have to do to get this working. No matter what at this point I think swaret for slackware is the best upgrade tool. It's simple, easy, and it resolves most dependency problems for me by default. Of course the simple answer would be to tell me just to stick with slackware but I'm trying to check out all the distros and be fair to them.. so I'm willing to listen to reasonable arguments on how apt-get is better and easier to use.. but I'm sure not seeing it right now..

EDIT1:
Let me give a specific error message I'm getting I can't resolve at all.. that doesn't make any sense either..

Code:
dpkg: error processing /var/cache/apt/archives/foomatic-db_20040303-1_all.deb (--unpack):
 trying to overwrite `/usr/share/foomatic/db/source/driver/gimp-print.xml', which is also in package foomatic-db-gimp-print
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/foomatic-db_20040303-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
It's this kind of stupid error that's making it absolutely impossible to resolve the continuous dependency problems.. it's absolutely insane.

EDIT2:
Ok, I looked around a bit and that one resolved by me removing the pkg with dpkg --force-all --remove foomatic-db and then install could continue.

However, now I have a package (gdm2) that will not leave.. it just won't let me continue because of a file it's trying to delete that it says doesn't exist.. I mean how can it break just because something isn't there that it wants to delete.. that's absolutely annoying...

EDIT3: Figured out how to delete gdm2 (easier than the other.. just use apt-get remove gdm2).. however now I'm having another error
no matter what I try it won't move forward. It says it something along the lines of exit status 2 on remove operation for gnome-session2.. nothing I do will get the process to move forward now. And, not only that it's already removed kde so I'm using lynx to post... *sigh*

Last edited by xanas3712; 05-11-2004 at 10:23 PM.
 
Old 05-12-2004, 05:01 AM   #2
Dead Parrot
Senior Member
 
Registered: Mar 2004
Distribution: Debian GNU/kFreeBSD
Posts: 1,597

Rep: Reputation: 46
OK, sorry I pointed you to a very general documentation. But I had (and continue to have) good intentions, honestly. It seemed to me that you are applying the Slackware methods to your Debian system and this can only produce a terrible mess. Debian has much more refined ways of doing things, just like APT is infinitely more refined than Swaret (which works fine in Slackware, though). It seemed to me that if I pointed you to a document that explained some Debian basics, this would give you a good start.

I still think you should give this document, called Debian Reference, a second look.
http://www.debian.org/doc/manuals/re...erence.en.html
You are not expected to read everything in one go. Rather, browse it and have a quick glance at any topic that seems interesting. It's also useful to bookmark this document, because it really is a rather good introduction into Debian and if you cannot find answers to your Debian-related questions elsewhere, you'll probably find them by studying this document a bit closer.

But you wanted more precise advices. I think you are correct in saying that you should log out of X before trying to upgrade your system. At least, you should log out of KDE before you attempt to upgrade KDE. The Debian tool that allows you to control services is called "update-rc.d". There are many other similar Debian-specific tools that you should use in Debian instead of the Slackware methods. The Debian Reference I pointed out introduces most of these tools. There's also an ncurses frontend for update-rc.d, but you should learn also how to use update-rc.d without this frontend.

So my precise advice is, do this:
# apt-get install rcconf
# rcconf
Then uncheck gdm in the rcconf program. Then reboot.
After this you should be able to log into console without starting X first.

Then su to root, do "nano /etc/apt/sources.list" and add these two lines:

deb ftp://ftp.debian.org/debian testing main contrib non-free
deb-src ftp://ftp.debian.org/debian testing main contrib non-free

Also comment out other lines you may have in sources.list so that these added lines are the only ones that don't begin with the character #. The "testing" in these lines refers to Sarge -- Woody would be "stable" and Sid would be "unstable".

After you've written the sources.list, you can do:
# apt-get update
# apt-get dist-upgrade
and if there's problems, you can try to fix them by doing:
# apt-get -f install

In general, your upgrades will be more successful if you initially make just a minimal installation, then do upgrade, and only after your base system is up-to-date you should start installing additional programs. Upgrading from Woody to Sarge and from Sarge to Sid are often successful (especially with the minimal initial installation) but downgrading from Sid to Sarge or from Sarge to Woody is likely to break your system.

BTW, you should know that when you install new applications, apt-get only installs the dependencies that your applications won't run without. But apt-get won't install the additionally "recommended" or "suggested" dependencies, although it is often wise to follow these recommendations and suggestions. The smarter frontends for apt-get are Aptitude (for console) and Synaptic (for X sessions) and they default to installing also the recommended dependencies, so you should use these programs to install any new applications.

Hope this helps -- and I still think you should read the Debian Reference and learn to do things the Debian way.


PS. If this upgrading business just doesn't seem to work, you might want to give the new Sarge Debian-installer a try before deciding that you've had enough of Debian.
http://www.debian.org/devel/debian-installer
It's still beta but if it works for you, you'll get a pretty much up-to-date Sarge system to start with.

Last edited by Dead Parrot; 05-12-2004 at 05:42 AM.
 
Old 05-12-2004, 02:32 PM   #3
xanas3712
Member
 
Registered: Apr 2004
Distribution: Slackware/Mandrake/Debian (sarge)
Posts: 266

Original Poster
Rep: Reputation: 30
No.. don't take that as an insult or anything.. it just wasn't specific enough.. and it was very very long It was a lot of information and more than I wanted to read at the time.

Sorry if I seemed ungrateful.. not the way I wanted to come off but I'm sure it's the way I stated it.
 
Old 05-12-2004, 05:31 PM   #4
psilo
Member
 
Registered: May 2004
Location: Holland
Distribution: Debian
Posts: 33

Rep: Reputation: 15
Only Sarge sources will get you in trouble

I recommend adding a sid source line to your sources.list and pin on testing. Sometimes you need a sid package to solve things in testing. Testing is not a distro meant to be used on it's own. It is automatically generated and therefore it is not garantueed it's combination of packages work. man apt_preferences to learn about pinning in a /etc/apt/preferences file.
 
Old 05-12-2004, 06:24 PM   #5
lynrees
LQ Newbie
 
Registered: Jan 2003
Location: Cymru Wales)
Distribution: Debian (Sarge & Sid)
Posts: 21

Rep: Reputation: 15
new debian installer

A better idea I think is to use the new (beta) debian installer http://www.debian.org/devel/debian-installer/

It will install sarge with no fuss! highly recommended.
 
Old 05-13-2004, 01:54 AM   #6
xanas3712
Member
 
Registered: Apr 2004
Distribution: Slackware/Mandrake/Debian (sarge)
Posts: 266

Original Poster
Rep: Reputation: 30
ahh.. great deal.. if this work as intended you rock.. but either way thanks

(realized that link was given in the other response so thanks to you as well.. I was going to table this for awhile but since this installer is here I figure going at it again today..)

Last edited by xanas3712; 05-13-2004 at 01:58 AM.
 
Old 05-13-2004, 04:58 AM   #7
xanas3712
Member
 
Registered: Apr 2004
Distribution: Slackware/Mandrake/Debian (sarge)
Posts: 266

Original Poster
Rep: Reputation: 30
Ok.. install from the beta was not without it's pains but I did get the system up and running. Something I was able to do before but not as easily as this time around. Sadly however, I couldn't manage to get the video drivers working for my Radeon 9800 pro.. so far mandrake is the only linux version that's been able to manage that (and quite well I must say).. but yet mandrake is unstable.. lol
That's kind of the role I was hoping this would fill. I already have lots of apps installed on slackware so I was hardly going to trash it to switch to debian but I was thinking of having debian for games instead of unstable mandrake.. but oh well.. I'll figure it out later perhaps.. or maybe ati will just get off theirs and release a darn xfree 4.4 driver.
 
Old 05-13-2004, 05:15 AM   #8
lynrees
LQ Newbie
 
Registered: Jan 2003
Location: Cymru Wales)
Distribution: Debian (Sarge & Sid)
Posts: 21

Rep: Reputation: 15
Debian in at Xfree 4.3 at the moment.

Can you download the drivers from ATI?

Can I ask what pains you had with the new installer? I've used beta 2&3 but not 4.
 
Old 05-13-2004, 05:27 AM   #9
xanas3712
Member
 
Registered: Apr 2004
Distribution: Slackware/Mandrake/Debian (sarge)
Posts: 266

Original Poster
Rep: Reputation: 30
well there was 3 times it couldn't install the packages because of a failure. Those were corrected with an apt-get -f install. The most annoying error was one of the dpkg ones on .. what was that package.. um.. console-tools I think? And that was it.. only the console-tools error I was unable to resolve, but luckily I was able to simply go around it by doing apt-get install kde and then I was in kde and was able to use synaptic to get the rest of what I needed installed. Oh, btw.. no doubt synaptic is a nice piece of work.. it's very nice. I'm not a fan of everything but at least it's very nice and easy to use.

Oh, and the ATI drivers.. I downloaded those and used alien to convert the package (rpm) to deb.. and then I installed it.. went to the source directory and compiled with sh make.sh and sh make_install.sh. Before this I had updated my kernel to 2.6.6 (compiled by me from a config file I have setup that works great on my slackware system and supports my hardware).. and so I had some problem with QT_modules.. I did a search for that and found out I needed module loading tools or whatever. I downloaded that followed some instructions ./configure \prefix-all or make moveold ./configure make make install ./generate-modules.conf and I got that problem resolved..

Then.. after having that resolved I started up X again with all the modules in their places (at least the ATI installer gave no errors). I got kde up again with dual head mode (which didn't work like it did in mandrake) and kept getting the stupid kinitrand error on startup (which disables my ability to change monitor resolution in kde).. anyway.. so I'm just wanting to test the driver.. so I exit kde.. go to my xinitrc and copy a backup, and then change the last line of the new one to
exec /home/user/ut2004/ut2004
I save.. startx again.. x starts.. ut2004 splash comes up.. goes away.. I sit there for a minute. I ctrl alt bkspace and there is an error [drm] fglrx unable to load.. or something like that.. didn't say the file was missing as it had earlier on when I tried it but said there was some kind of error so DRI was disabled.

Don't ask me what caused it.. and I'm completely clueless on why it's giving me trouble as I had 0 trouble with it in mandrake which basically does the same thing except for the fact it runs the compile scripts for you. Oh, also I turned off dual head mode just in case that was the problem to try it on the one single screen.
 
Old 05-13-2004, 05:40 AM   #10
lynrees
LQ Newbie
 
Registered: Jan 2003
Location: Cymru Wales)
Distribution: Debian (Sarge & Sid)
Posts: 21

Rep: Reputation: 15
Have you still got the XFree86 config file from mandrake...?

If you have, check it and tweak you're Debian XFree86 config. Something I used to do in the past as well (though not anymore as the new installer is good) was boot a copy of knoppix and steal the XFree86 config from there! This can give good results, though it is cheating!

Sounds like your nearly there.
 
Old 05-13-2004, 05:57 AM   #11
xanas3712
Member
 
Registered: Apr 2004
Distribution: Slackware/Mandrake/Debian (sarge)
Posts: 266

Original Poster
Rep: Reputation: 30
well I ran fglrxconfig and as far as I know it should produce the same results regardless no?

Worth a try though hehe..
 
Old 05-14-2004, 06:19 AM   #12
psilo
Member
 
Registered: May 2004
Location: Holland
Distribution: Debian
Posts: 33

Rep: Reputation: 15
console-common

The console-common problem can be solved by running (as root):

# sh -x /var/lib/dpkg/info/console-common.preinst

And selecting the right keymap.

It's bug #242594.

When running sarge/sid bugs.debian.org is a very useful resource. Almost every problem has a work-around.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Helping setting up a proper backup system scoops98 Linux - Software 5 06-22-2005 01:03 PM
Debian Upgrade may brake system !!! rvijay Debian 2 06-12-2005 08:26 PM
Proper steps to upgrade machiner Linux - Distributions 1 09-27-2004 12:53 PM
Best method to upgrade HDD of RH Linux 6.0 (lilo boot) Noorul Linux - Software 3 08-26-2004 01:18 PM
best method to upgrade RH Linux 6.0 harddisk with lilo boot Noorul LQ Suggestions & Feedback 1 08-25-2004 06:32 AM


All times are GMT -5. The time now is 04:48 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration