You are not logged in.
Pages: 1
Hi,
Seems cifs-utils has replaced the smbfs package in rolling but smbfs still appears as a dependence of smbbox; this can be a little confusing when you view smbbox in TazPanel and see that one of the dependences (smbfs) is not installed.
But installation goes well, TazPkg finds smbs as missing package but installs linux-cifs and cifs-utils.
In the same way, using the 64bit version: in TazPanel, when looking at dependences of packages that need kernel modules, you can believe that modules aren't installed; ie cifs-utils -> linux-cifs is not installed (but linux64-cifs is); [c]tazpkg depends[/c] package_name also lists the name of the 32bit kernel modules
But I understand because packages are common to 32 and 64 bit versions.
By the way; 3 warning messages during the installation of samba:
[c]WARNING! Dependency loop between "cups-filters" and "cups".
WARNING! Dependency loop between "ghostscript" and "cups".
WARNING! Dependency loop between "gutenprint" and "cups".[/c]
Offline
Hi Ceel,
Seems cifs-utils has replaced the smbfs package in rolling but smbfs still appears as a dependence of smbbox; this can be a little confusing when you view smbbox in TazPanel and see that one of the dependences (smbfs) is not installed.
But installation goes well, TazPkg finds smbs as missing package but installs linux-cifs and cifs-utils.
By the way; 3 warning messages during the installation of samba:
WARNING! Dependency loop between "cups-filters" and "cups".
WARNING! Dependency loop between "ghostscript" and "cups".
WARNING! Dependency loop between "gutenprint" and "cups".
Offline
Hi Ceel,
this can be a little confusing when you view smbbox in TazPanel and see that one of the dependences (smbfs) is not installed.
But installation goes well, TazPkg finds smbs as missing package but installs linux-cifs and cifs-utils.
Yes, it is confusing.
Here, in the TazPkg, exists term "equivalent packages". They are described in the [c]packages.equiv[/c] database (/var/lib/tazpkg/packages.equiv). See the line:
[c]smbfs=cifs-utils[/c]
This statement means: you can use smbfs or cifs-utils.
If some package needs smbfs, and smbfs not installed — it may use cifs-utils if cifs-utils previously installed (execuse my bad English).
I just fixed way TazPanel show info about dependent packages.
How it was?

Note, freetype is not installed, but all dependencies are resolved. How? I use equivalent package freetype-infinality (at allows sub-pixel rendering).
Note, that I can't put freetype-infinality into dependencies — it is not true. As well, I can't put "installed" icon near freetype package — it is not true too. You can click link and see that package really not installed.
So, my solution:

Note: freetype→freetype-infinality
It means: we need freetype (and it not installed), but → we have freetype-infinality installed. And link will show you info about installed one.
Solution available in the tazpkg-831 (Cooker).
Offline
Pages: 1
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]