Re: apt-get/dselect-problem
On Tue, Jul 10, 2001 at 08:04:55PM +0200, Martin Bretschneider wrote:
> moin moin Joost!
>
> On Tue, 10 Jul 2001 01:33:02 +0200 you were able to write:
>
> [...]
> > > deb cdrom:[Debian GNU/Linux 2.4 _Sid_ - fsn.hu's i386 Binary-1
> > > (20010525)]/ unstable contrib main non-US/contrib non-US/main
> > > non-US/non-free non-free
> > >
> > > deb ftp://ftp.debian.org/debian sid main contrib non-free
> > >
> > > So what shall I do?
> >
> > Comment out the ftp uri, it is polluting the available list with much
> > newer versions than what is on the cd's. Then run "dselect update".
>
> But if I wanna update some packages from ftp what should I do?
> Delete the #?
If you want to update from ftp, uncomment all but the ftp uris.
If you do not want to update all packages, put the ones that you do
not want to upgrade on hold. If you want to track only a few packages,
put everything on hold first and then unhold the few.
This is best done by selecting the sections headers of groups of packages
and setting the whole group on hold with 'H'. Simply acknowledge any
suggestions by dselect to set other packages also on hold.
When you've put all installed packages on hold, quit dselect and
update /etc/apt/sources.list. Go back to dselect and and run update.
Then go back to select and unhold the packages you want to upgrade with
'G'. Possibly dselect will detect some unresolved dependencies, in that
case unhold the packages that are must also be upgraded because of some
depends or conflicts.
Then run install from the menu.
Or, without using the dselect menu:
dselect select # set all packages on hold
edit /etc/apt/sources.list # remove cd, put in ftp
dselect update # update new available packages list
dselect select # unhold packages you want upgraded
dselect install # upgrade selected packages
Be careful that you set packages on hold before updating the available
packages list. In the new list, dependencies may have changed or
been added. If all packages are already on hold, you should not have
to deal with these changes.
If you do this the wrong order, it will be very confusing, because dselect
will first try to update the selections to accomodate for any new depends
or conflicts of all selected packages. Moreover, when you then try to set
all packages on hold, dselect will be hopelessly confused, as will you,
soon enough. Unless you completely understand what is going on and are
able to oversee multiple dependency structures on dozens of packages,
the only way out is pressing 'X' repeatedly and updating the available
packages list to the cdrom versions before entering dselect select again.
Cheers,
Joost
Reply to: