Upgrading packages from Alien Bob Repo
I compiled some packages, especially development/multimedia libraries from Slackbuilds.org in order to run dvds,mp3s etc.And,now I want to upgrade the installed packages from Alien Bob repository.Is it possible to upgrade by using slackpkg or upgradepkg command?
I am running 64bit Slackware-Current |
You can use 'upgradepkg --reinstall newpackagename [newpackagename2]' to do this.
As the packages you want to install are not "official", then slackpkg will not recognise them. |
Thanks for the quick reply.
But,I really don't want to manually download a package and then upgrade it by using upgradepkg. I want to upgrade those packages like "slackpkg upgrade-all" command upgrade does by specifying the Alien Bob repository's url .Bcoz,there are more than 50 packages which I have compiled from Slackbuilds |
Quote:
|
I am not aware of a tool like slackpkg for accessing http://connie.slackware.com/~alien/slackbuilds/
You could automate this somewhat by: 1) Creating a list of files to be upgraded, perhaps starting with 'ls /var/log/packages | grep SBo' 2) Use some sed magic to modify that file so that you can copy the list into a download program such as lftp. 3) Collect the downloaded files in a single directory so that you can run 'upgradepkg --reinstall *.t?z' For fifty odd files you would probably also want to check md5sums on the downloaded files. |
Thanks for the reply.I will try both of your methods
|
You can also use slapt-get.
|
Quote:
I never use slapt-get before ,but if it works then is there any conflict in packages,i.e installation of two packages twice.Because as far as I know Slackbuilds use _SBo in their package naming and Alien Bob use alien. Correct me if I am wrong. IS it possible to change the mirror of sbopkg uses to Alien Bob's repository?Bcoz,what it does is sync your installed package list with the Slackbuids.org and then it performs the upgrade. Thanks by the way |
Quote:
|
If I understand this correctly you want to replace all your SlackBuild packages with equivalent ones from Alien Bob's repository (where they are available).
If yes, here is one way to do the following: Quote:
Code:
( cd /var/log/packages/ ; ls *SBo | rev | cut -f 4- -d - | rev | sed 's,.*,/\0-,' > /tmp/SBo-pkg.lst ) So perhaps something like this: Code:
wget -qO- http://connie.slackware.com/~alien/slackbuilds/FILELIST.TXT | grep -f /tmp/SBo-pkg.lst | sed -nr 's,.* \./(.*/pkg64/13.37.*(t.z|md5|asc))$,http://connie.slackware.com/~alien/slackbuilds/\1,p' > /tmp/alien-pkg.urls When the list looks correct to you, just switch to a suitable empty directory and issue. Code:
wget -i /tmp/alien-pkg.urls Code:
cat *.md5 | md5sum -c Code:
find . -name "*.asc" -maxdepth 1 -printf "\n%f\n" -exec gpg --verify {} \; Code:
upgradepkg --reinstall *.t?z |
Edit: Deleted and updated examples in the previous post so that it is easier to follow
|
Thanks ruario.Great answer
|
@deto86: I updated the first example to create a better grep list and avoid false positive matches (e.g. previously if you had an SBo package with a very short name like 'di' it might have matched other packages much later on). I also updated the second example so that /tmp/alien-pkg.urls includes signature files, in case you want to be extra cautious. ;)
|
Are we having fun yet? :-D
|
Yes we are, break out the chocolate and let's celebrate! ;)
|
All times are GMT -5. The time now is 10:52 AM. |