[PlanetCCRMA] how to upgrade a package without access to internet repository?

[Alex Timmer]

 --- Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU> wrote: >
> > > due to the dependencies  =). anyway, i managed to forcefully
> update
> > > > everything with rpm except JACK (have 0.51, need >0.62)
> > > 
> > > Hmmm, strange, what is it complaining about?
> > 
> > now i think about it again, i only got scared from the list of
> > dependencies i would break; i actually think rpm would install
> it.
> > will try tonight.

i tried but stopped because newer JACK requires a newer GLIBC which
probably requires... etc etc.   :)


> Yes, I was not thinking at all (too much work, brain burnout), your
> current jack is very old and at some point all jack-aware
> applications
> got a "Requires:" tag that explicitly wants a newer one. That's
> probably
> why there were so many dependencies. 
> 
<SNIP>
> > was there not some discussion a while a ago about a method to
> make
> > your own cdroms out of the (up-to-date) repository? i could help
> wiht
> > scripting, now if i knew where those dependencies are hidden... 
> ;-)
> 
> They are part of the apt database. I have not even tried to think
> of a
> way to create "custom" iso images. I imagine it should be possible
> to do
> as the data is there in some form. 

in the archives i found what i was referring to earlier:
http://ccrma-mail.stanford.edu/pipermail/planetccrma/2003-January/001073.html


> > > You can always download and install manually, but you should
> try
> > > not to use --force or --nodeps, otherwise the apt database
> won't be useful
> > > in the future and chances are that things will not work right
> (after
> > > all, that is what dependencies are for). 
> > 
> > you are right, an 'apt-get update' now tells me this was not too
> > smart (more precise, apt-get detects more than one version of the
> > same pkg).
> 
> You will need to erase those duplicates and reinstall. I think the
> right
> option to rpm -e is "--allmatches", that will erase all installs of
> the
> same name (and version). Obviously you don't want to use rpm -e
> --allmatches if you are dealing with a vital package like glibc :-)
> 
> To see what errors you have you can do a:
>   apt-get check
> That will check the package database for consistency. 
> 
> -- Fernando

thanks, i'll try that as learning experience  :) 

cheerio, ALEX

________________________________________________________________________
Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://uk.messenger.yahoo.com/