Getting apt-get

[nathan r. hruby]

On Fri, 15 Nov 2002, Stephen Reiach wrote:

> On Fri, 15 Nov 2002 14:21:56 -0500
> Bondtrails <bondtrails@earthlink.net> wrote:
> 
> > How can I find out all the dependencies to apt-get, and how cat I get 
> > them?
> > 
> 
> you're missing something.  All the required packages should be on your
> 2.3 CD. You may want to search this ML if anyone actually wrote down the
> exact course of action. [ps write it down and post it!]
> 

One thing that no one has tried before it to try in install apt with yup 
(which in theory should be able to handle deps for you.)

Here's how I would do it (note: this isn't tested... if it breaks you keep 
both pieces)
* = optional but recommended step
- = required step

* Backup anything you want to keep
* Stop all services (sendmail, httpd, etc..), including X drop to a 
  console.
- Edit /etc/yup.conf with info for the YDL 2.3 release (see below).
  (or you can try running 'yup config dist', i prefer the former)
- Run 'yup clean all'
* Run 'yup config mirror' (adding the CD might be an option
- Run 'yup update yup'
- Run 'yup install apt'
- Edit /etc/apt/sources.list to point at 2.3 distros, not 2.2
* run apt-cdrom add for each CD in YDL-2.3 if you have them
- Run 'apt-get upgrade'
- Run 'apt-get dist-upgrade'
* Wash-rinse-repeat as needed till apt says there's nothing to upgrade
- Run '/sbin/yaboot'
- apt-get install kernel-2.4.19-4a
- Run '/sbin/yaboot'
- Reboot

--- STOCK /etc/yup.conf from YDL-2.3
.master                 http://www.yellowdoglinux.com/yup/yup.master.txt
.dist-option            Yellow Dog Linux release 2.3
.arch-option            ppc
.begin                  mirror-option
   .name                   Yellow Dog Linux release 2.3
   .addr                   ftp://ftp.yellowdoglinux.com/pub/yellowdog/yellowdog-2.3
   .arch                   ppc
.end
--- END STOCK

Thw yup part of this should upgrade/install many packages including
glibc*, rpm*, several (if not all) of the kde packages if you have KDE
isntalled, and a few other.  The archives have a better lising of what
files get/need upgrading, though that was from 2.1 I think...

Things that might happen:
- yup will die leaving the package system is disarray (rpm --rebuilddb 
  should fix this)
- yup won't be able to deal with the upgrade and fail before doing 
  anything
- Massive amounts of time could be killed, resulting in the need for 
  co:ff:ee:co:ff:ee and a slight resentment at the whole of technology
- Tons of other things I can't think of.

If this solution works, please let the list know plus nay problem you've 
had or things you did differently.

-n
-- 
----------------------------------------
nathan hruby <nathan@drama.uga.edu>
computer services specialist
uga drama
http://www.drama.uga.edu/support/
----------------------------------------