Slpkg New Slackware packaging tool

rng · 01-17-2016, 08:37 AM

I have following problem: slpkg is trying to get files for Slackware version "14.2" (see url in output below) and obviously it is failing:

Quote:

# slpkg update

Check and update repositories:

Check repository [slonly] ...
[1/1][ Download ] --> PACKAGES.TXT

--2016-01-18 01:28:17-- http://packages.slackonly.com/pub/pa...6/PACKAGES.TXT
Resolving packages.slackonly.com (packages.slackonly.com)... 45.58.49.216
Connecting to packages.slackonly.com (packages.slackonly.com)|45.58.49.216|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2016-01-18 01:28:18 ERROR 404: Not Found.

+==============================================================================
| Download 'PACKAGES.TXT' file [ FAILED ]
+==============================================================================

Would you like to continue [y/N]?
bash-4.3#

The entry "RELEASE=stable" is there in the file /etc/slpkg/slpkg.conf . The slpkg version is 3.0.5
How can I correct this?

Edit: I found that /etc/slackware-version file had "Slackware 14.2" rather than "Slackware 14.1". Correcting this solved the problem and slpkg is working well. I do not know how this recently installed Slackware had "Slackware 14.2" entry.

rng · 01-19-2016, 11:32 AM

slpkg works very well but it does not pick up all dependencies. For example, I installed following and some dependencies were missed:

Code:

Application : 	        missed dependencies

abiword: 		wv, cyrus-sasl-lib-2
Thunar: 		exo, xfce4util, libxfce4ui, xfconf
xoscope: 		gtkdatabox

But overall, package management is much easier with slpkg.

dslackw · 01-19-2016, 11:39 AM

Quote:

Originally Posted by rng

slpkg works very well but it does not pick up all dependencies. For example, I installed following and some dependencies were missed:

Code:

Application : 	        missed dependencies

abiword: 		wv, cyrus-sasl-lib-2
Thunar: 		exo, xfce4util, libxfce4ui, xfconf
xoscope: 		gtkdatabox

But overall, package management is much easier with slpkg.

From what repository?

rng · 01-19-2016, 06:50 PM

xoscope and abiword from slackonly; Thunar from slackware. The missing dependencies may be due to my incomplete Slackware installation also, since I had selected only A, AP, D, L, N, X and KDE packages during installation.

dslackw · 01-19-2016, 07:37 PM

It is repository issues.

Slackware repository it has not reference dependencies.
Slonly repository sometimes no reference dependencies for packages.

travis82 · 01-19-2016, 10:55 PM

Quote:

Originally Posted by rng

xoscope and abiword from slackonly; Thunar from slackware. The missing dependencies may be due to my incomplete Slackware installation also, since I had selected only A, AP, D, L, N, X and KDE packages during installation.

At the moment many packages in slackonly repository have empty REQUIRED line on it's PACKAGES.TXT file. Hence, whatever package manager you use, some dependency problems are unavoidable.

Regarding Thunar, don't try to install it from slackware repository as you haven't installed Xfce desktop and slackware repository doesn't provide dependency information for slpkg. Use salix repository instead. Just uncomment salix repository from /etc/slpkg/repositories.conf or add nearest salix mirror using slpkg repo-add command.

rng · 01-20-2016, 09:01 AM

Thanks.

Can slpkg be used to find 'orphan' library packages or dependencies - i.e. those whose main package has been removed and which are now lying unneeded on the system?

Didier Spaier · 01-20-2016, 09:19 AM

I do know (I still have to give slpkg a go), but usm can.

rng · 01-20-2016, 11:41 AM

I tried to see in 'man usm' and on its web page (http://sourceforge.net/p/usm/wiki/Home/) but could not find its command to find orphan packages. What usm command can I use?

Didier Spaier · 01-20-2016, 11:46 AM

You will get the man page after having installed the package.

rng · 01-20-2016, 11:56 AM

I already have it installed and I have seen the man page but could not find the command. One could possibly list all library files and feed each of them into 'usm -s' command one by one using xargs. How do you find orphan packages in usm?

Didier Spaier · 01-20-2016, 12:26 PM

What do you mean by "orphan package"?

travis82 · 01-20-2016, 01:45 PM

@rng
You mean something like "apt-get autoremove". No, slpkg doesn't provide such an option. However if you use it to remove third-party packages by "slpkg -r --deps <packagename>" you don't have any third-party orphan library on your system. Genuine orphan slackware libraries are different story and I don't think slpkg, usm and other package managers have the ability to find and remove them.

Didier Spaier · 01-20-2016, 02:00 PM

@rng: maybe you meant by "orphaned library" a library not shipped in any installed Slackware package. This can be checked with some pseuod-code like

Code:

for LIBRARY in <list of all installed libraries>; do
    if ! grep -wg $LIBRARY /var/log/packages/*; then
        printf  b "The library $LIBRARY is orphaned.\n"
    fi
done

But if a library was installed another way than as shipped in a Slackware package regularly installed, then removing it could have negative consequences.

Of course you'd have to take care of the symlinks as well, that are usually recorded in /var/log/scripts.

travis82 · 01-20-2016, 02:39 PM

@Didier
I think by orphan libraries he means libraries which are not dependency of installed packages.