spi issues

[icaroperseo]

Good day community!

I've had problems with spi again. I installed packages using this application and the end of the process indicates that the previously installed packages as dependencies are still missing. This behavior has already been previously repeated when I trying to install Pandoc (http://forum.salixos.org/viewtopic.php? ... 405#p37341). This time it was presented when I trying to install gnome-vfs which requires libbonobo and gnome-mime-data as dependencies same as previously installed through spi. To solve the problem I did the following:

Code: Select all

sudo slapt-src -n --install gnome-vfs

I really worry about this situation because I do not like to have inconsistencies in my system in the future. Is there any way to avoid or correct this situation? I'm in the provision of help in any way possible to avoid these small bugs so if you need anything else just let me know!

Thanks in advance...

[laprjns]

I cannot confirm a bug here on my Salix64-XFCe 14.1.system. I installed gnome-vfs using:

Code: Select all

rich[~]$ sudo spi -i gnome-vfs

and spi installed the following packages, all from Slackbuild without problems.

Code: Select all

gnome-vfs-2.24.4-x86_64-3_SBo
libbonobo-2.32.1-x86_64-2_SBo
ORBit2-2.14.19-x86_64-3_SBo
gnome-mime-data-2.18.0-x86_64-2_SBo

Also gave pandoc a try and again had no problems. This time spi downloaded, build and installed 30 packages from Slackbuild and installed one package (ghc) from the Salix repository.

Code: Select all

andoc-1.11.1-x86_64-1_SBo
haskell-HTTP-4000.2.8-x86_64-1_SBo
haskell-network-2.4.1.2-x86_64-1_SBo
haskell-texmath-0.6.1.3-x86_64-1_SBo
haskell-highlighting-kate-0.5.3.7-x86_64-1_SBo
haskell-regex-pcre-builtin-0.94.4.5.8.31-x86_64-1_SBo
haskell-regex-base-0.93.2-x86_64-3_SBo
haskell-blaze-html-0.5.1.3-x86_64-1_SBo
haskell-blaze-markup-0.5.1.4-x86_64-1_SBo
haskell-blaze-builder-0.3.1.0-x86_64-1_SBo
haskell-citeproc-hs-0.3.7-x86_64-1_SBo
haskell-xml-1.3.12-x86_64-1_SBo
haskell-parsec-3.1.3-x86_64-1_SBo
haskell-pandoc-types-1.10-x86_64-1_SBo
haskell-json-0.7-x86_64-1_SBo
haskell-syb-0.3.7-x86_64-1_SBo
haskell-tagsoup-0.12.8-x86_64-1_SBo
haskell-text-0.11.2.3-x86_64-1_SBo
haskell-extensible-exceptions-0.1.1.4-x86_64-1_SBo
haskell-zip-archive-0.1.3.3-x86_64-1_SBo
haskell-zlib-0.5.4.0-x86_64-1_SBo
haskell-utf8-string-0.3.7-x86_64-2_SBo
haskell-mtl-2.1.2-x86_64-1_SBo
haskell-transformers-0.3.0.0-x86_64-1_SBo
haskell-digest-0.0.1.2-x86_64-1_SBo
haskell-temporary-1.1.2.4-x86_64-1_SBo
haskell-random-1.0.1.1-x86_64-1_SBo
haskell-data-default-0.5.0-x86_64-1_SBo
haskell-dlist-0.5-x86_64-2_SBo
haskell-base64-bytestring-1.0.0.1-x86_64-1_SBo
ghc-7.6.3-x86_64-1tjb

I really worry about this situation because I do not like to have inconsistencies in my system

I thinking that the problem is unique to your system. Did you re-install slapt-src as gapan suggested in the pandoc thread? Also try to update your repositories using reposetup.

I'm in the provision of help in any way possible to avoid these small bugs so if you need anything else just let me know!

Can you post the last 10 to 20 lines from the output of the spi -i gnome-vfs

[icaroperseo]

I cannot confirm a bug here on my Salix64-XFCe 14.1.system.

Sorry I forgot to mention before but I use Salix64-Mate 14.1...

I thinking that the problem is unique to your system. Did you re-install slapt-src as gapan suggested in the pandoc thread?

Yes, I did (I uninstall it and install it once more if you refer to it) and there was no change.

Also try to update your repositories using reposetup.

This is new to me. Do I only should execute the following and select the mirror?

Code: Select all

sudo reposetup

Currently and previously I used http://salix.hostingxtreme.com/.

Can you post the last 10 to 20 lines from the output of the spi -i gnome-vfs

Does not matter if I installed it as follows?

Code: Select all

sudo slapt-src -n -i gnome-vfs

If so, how could I do this?

Thanks for replying...

[icaroperseo]

By the way, comes to my mind that the procedure I follow is:

Code: Select all

sudo spi --search "x-package"
sudo spi --show "x-package"
sudo spi --install "x-package dependencies"
sudo spi --install "x-package"

The reason I do this is because according to my own experience, sometimes the package managers are not correctly resolve dependencies, that is to say, the installation process is interrupted or simply not start to tell me that particular package is not installed and acts as dependence previous packet. In this way I avoid certain inconveniences or at least I think .

Please, if I do not explain correctly is because the English is not my primary language. I do not mind trying to explain better if necessary.

[laprjns]

I installed packages using this application and the end of the process indicates that the previously installed packages as dependencies are still missing

In oder to understand this better we need to recreate the error that was indicated in the console.. Could you please do the following.

First, uninstall gnome-vfs and any of it's dependencies that you may have installed

Code: Select all

$ sudo slapt-get --remove gnome-vfs libbonobo ORBit2 gnome-mime-data

Now try installing gnome-vfs again using spi.

Code: Select all

$ sudo spi --install gnome-vfs

if the build fails again, then copy the last 20 lines of log output from the console and past it here using the code tags.

[icaroperseo]

I installed packages using this application and the end of the process indicates that the previously installed packages as dependencies are still missing

In oder to understand this better we need to recreate the error that was indicated in the console.. Could you please do the following.

First, uninstall gnome-vfs and any of it's dependencies that you may have installed

Code: Select all

$ sudo slapt-get --remove gnome-vfs libbonobo ORBit2 gnome-mime-data

Now try installing gnome-vfs again using spi.

Code: Select all

$ sudo spi --install gnome-vfs

if the build fails again, then copy the last 20 lines of log output from the console and past it here using the code tags.

I am confused right now, everything worked correctly... What could be the problem now? I ask because I would like to avoid such problems. For all I know, there is a daemon running in background that updates the repository every certain period of time, right? Am I doing something wrong?

[gapan]

Yes. You're putting things in quotes. "Foo bar" means a single package named exactly like that, not two.

[laprjns]

I am confused right now, everything worked correctly..

Well I'm guessing that the slapt-src cache was not updated or there was something wrong with your slapt-srcrc file in /etc/slapt-get/ when you first attempeted to install via spi.

What could be the problem now?

There is no problem now, its working the way it is suppose to.

For all I know, there is a daemon running in background that updates the repository every certain period of time, right?

Yes there is a a deamon, salix-update-notifier, running in the background, but that is only updating from salix binary repository (i.e slapt-get). You need to manually update the Slackbuild cache by using either slapt-src --update or spi --update. So you should make it a habit to update the slapt-src cache before attempting to install new applications.

[icaroperseo]

Thanks guys, I'll take note of your suggestions. You rock!!!