Re: Autoup Upgrade
Bob,
Thanks for the clear and informative message.
I think this should be included with the autoup.sh documentation, it
certainly explains things not described there.
Gregory Guthrie
---------------------------------
At 10:53 PM 6/28/98 -0400, Bob Hilliard wrote:
>Hi,
> During the upgrade, autoup.sh must remove several critical
>packages in order to upgrade them i.e. in bo, perl is one package; in
>hamm perl is provided by perl-base and perl. The hamm version of perl
>depends on perl-base, but perl-base conflicts with the bo version of
>perl. Therefore it is necessary to remove the bo version of perl.
>
> Since many packages depend upon perl, dpkg must deconfigure these
>packages, then remove perl. It then installs perl-base and perl in
>sequence and configures the packages that were unconfigured.
>During that process, a number of alarming warning messages are
>generated.
>
> If autoup.sh completes normally (displays a message saying you
>now have a libc6 system, and discusses wtmp and utmp), all of these
>warning messages may be ignored.
>
> When you enter dselect after autoup finishes, the best course of
>action is to use the access, update and install modules - don't even
>enter the select module. In that case all packages on your system
>that have an upgraded version (almost all of them) are automatically
>upgraded without any further action on your part. You are then free
>to use the select function to add any package you might desire. Most
>development libraries are removed by autoup.sh, and are not
>automatically replaced. Autoup.sh creates a file
>"removed-<today's_date>" in the current directory recording the
>packages that were removed. This provides a guide to the packages
>that should be reinstalled with dselect or manually with dpkg -i.
>
>Bob
>-- _
> |_) _ |_ Robert D. Hilliard <hilliard@flinet.com>
> |_) (_) |_) Palm City, FL USA PGP Key ID: A8E40EB9
>
>
>Gregory Guthrie <guthrie@mum.edu> writes:
>
>> I just did an upgrade bo --> hamm using autoup.sh.
>>
>> Amazing. But, there are a number of steps which left me cold; and flipping
>> a coinn for the right action.
>>
>> 1) during the autoup it had seeral "conflicts", adn it was not clear to me
>> if I needed to do anything about them. E.g. I think it tried to remove
>> something that depended on Perl, but I had perl installed, or something...
>> "dependency problems .. libwww-perl depends on Perl, but perl is not
>> installed.
>> ... libnet
>>
>> Anyway, there was no clear indication if all was OK, if it was a comment,
>> or if some remedial action was needed (later).,
>>
>> 2) After update, it says "now use dselect to upgrade the rest of your
>> system", then reboot.
>>
>> ?? How do I know what to upgrade? I would like to say; "whatever needs an
>> upgrade, if I have it installed, do it."
>> Instead, I had to go through dselect, look at hundreds of packages, try to
>> remember which I had selected, and decide if they need update. Am I missing
>> something here?
>>
>> Greg Guthrie
>> --------------------------------------------------------
>> Dr. Gregory Guthrie
>> guthrie@mum.edu (515)472-1125 Fax: -1103
>> Computer Science Department
>> College of Science and Technology
>> Maharishi University of Management
>> (Maharishi International University 1971-1995)
>> --------------------------------------------------------
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>>
>>
>>
>
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
--
Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
Reply to: