LinuxQuestions.org - [SOLVED] Strange behavior

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Strange behavior (https://www.linuxquestions.org/questions/slackware-14/strange-behavior-4175642459/)

Strange behavior

Recently, I was updated from Slackware 14 to 14.2 using a disk. In installation time of a system I specified that I want to install packages from network. Specified a mirror, updating took place normally. But, began to delete not tiresome to me applications, I noticed some strange behavior of removepkg
Example:
If i want unistall any program, removepkg give out in reply

Code:

 removepkg /var/log/packages/calligra-2.9.11-x86_64-26 

No such package: calligra-2.9.11-x86_64-26. Can't remove.

This mistake will appear during removal of any package.
Further, if I install the application, and then I will try to remove it, then wonderfully I will not find it in /var/log/packages

Code:

bash-4.4# upgradepkg --install-new /tmp/geany

geany-1.31.0-x86_64-1_SBo.tgz          geany-plugins-1.31.0-x86_64-1_SBo.tgz              

bash-4.4# upgradepkg --install-new /tmp/geany-1.31.0-x86_64-1_SBo.tgz 



+==============================================================================

| Installing new package /tmp/geany-1.31.0-x86_64-1_SBo.tgz

+==============================================================================



Verifying package geany-1.31.0-x86_64-1_SBo.tgz.

Installing package geany-1.31.0-x86_64-1_SBo.tgz:

PACKAGE DESCRIPTION:

# geany (small and lightweight Integrated Development Environment)

#

# Geany is a text editor using the GTK2 toolkit with basic features of

# an integrated development environment. It was developed to provide a

# small and fast IDE, which has only a few dependencies from other

# packages. It supports many filetypes and has some nice features.

#

# Homepage: https://www.geany.org/

#

Executing install script for geany-1.31.0-x86_64-1_SBo.tgz.

Package geany-1.31.0-x86_64-1_SBo.tgz installed.

bash-4.4# upgradepkg --install-new /tmp/geany-plugins-1.31.0-x86_64-1_SBo.tgz 



+==============================================================================

| Skipping package geany-plugins-1.31.0-x86_64-1_SBo (already installed)

+==============================================================================



bash-4.4# removepkg /var/log/packages/ge

geeqie-1.4-x86_64-2              genpower-1.0.5-x86_64-3          gettext-0.19.8.1-x86_64-5        getty-ps-2.1.0b-x86_64-4        

gegl-0.4.12-x86_64-1            getmail-5.7-x86_64-1            gettext-tools-0.19.8.1-x86_64-5  gexiv2-0.10.8-x86_64-1

What became the reason of such behavior?

what about running?

Code:

$ upgradepkg --reinstall /tmp/geany-1.31.0-x86_64-1_SBo.tgz

Does it install it? does geany appear on /var/log/packages?

Also, do

Code:

$ ls /var/log/packages/ge*

(Instead of tab-tab)

What about disk usage? it isn't full, is it?

And does dmesg show any error?

I attached the file in an investment. Did not find anything interesting.

Quote:

What about disk usage? it isn't full, is it?

The root section of the file system is engaged at only 12GB of 50GB.
The most interesting, in directory/var/log/packages/is not present files of those programs which I compiled and installed independently.

Code:

bash-4.4# ls /var/log/packages/ | grep calligra

calligra-2.9.11-x86_64-26

bash-4.4# ls /var/log/packages/ | grep geany

bash-4.4#

Quote:

Originally Posted by DenisAndreevich (Post 5926612)

Recently, I was updated from Slackware 14 to 14.2 using a disk.

Perhaps you should be more specific about what disk that was, and what commands you used to update.
Because what I notice (kernel version in your dmesg output and package versions you mention) you are running slackware-current and not Slackware 14.2.
If you upgraded from 14.1 directly to -current and skipping 14.2 there's going to be some challenges for you.

Quote:

Originally Posted by Alien Bob (Post 5926986)

I took iso from the http://www.slackware.com/torrents/sl...ll-dvd.torrent page. Then, when the fitter was started, one of questions was from where to install a system. I chose to establish on network and specified a mirror http://mirror.yandex.ru/slackware/slackware64-current/. Further, executed a system configuration (timezone, elilo etc) and all. I correctly understand that it would be at first better to install packages from a disk, and then to update them on network?

P.S Generally everything works as expected. I normally installed the driver of Nvidia. I normally collect packages, I listen to music, I watch film and I use Firefox

Going from Slackware 14 to Slackware-current is a version jump of three versions. Not good if you don't totally read the changelogs from each version. There will have been a lot of packages removed, and a lot of packages added. This will account for the weird behavior you are seeing and will probably see a lot more yet.

A clean install is best for a multiple version jump.

II remembered an important thing (as it seems to me) why in installation time chose current repository. When I selected the mount endpoints, I indicated that the root and boot partition would be formatted. I did not format the home directory.
My fstab:

Code:

/dev/sda3        /                ext4        defaults        1  1

/dev/sda2        /boot            ext4        defaults        1  2

/dev/sda4        /home            ext4        defaults        1  2

/dev/sda1        /boot/efi        vfat        defaults        1  0

#/dev/cdrom      /mnt/cdrom      auto        noauto,owner,ro,comment=x-gvfs-show 0  0

/dev/fd0        /mnt/floppy      auto        noauto,owner    0  0

devpts          /dev/pts        devpts      gid=5,mode=620  0  0

proc            /proc            proc        defaults        0  0

tmpfs            /dev/shm        tmpfs      defaults        0  0



UUID="C0A4DC6AA4DC6486" /home/denis/SteamNtfs/  ntfs-3g    user,users,gid=users,fmask=113,dmask=002,locale=ru_RU.UTF-8 0 0

UUID="86BEE2D6BEE2BDB5" /home/denis/WindowsHome/          ntfs-3g    user,users,gid=users,fmask=113,dmask=002,locale=ru_RU.UTF-8 0 0

Several months ago pkgtools had a change made to it in Slackware-current. In short, the directories where pkgtools store the package "database" was moved from /var/log to /var/lib/pkgtools/.

My guess is that 14.0 left remnants behind of the old package "database" location, even though you upgraded to Slackware-current. It may be possible to correct this on your system. However it is likely more efficient to do a fresh installation of Slackware-current instead.

Please post the output of:

Code:

ls -l /var/log

ls -l /var/lib/pkgtools/

Please use code tags.

Quote:

Originally Posted by mralk3 (Post 5927035)

Code:

ls -l /var/log

ls -l /var/lib/pkgtools/

Please use code tags.

I just reinstalled the system. The same iso burned to disc. I formatted the root and boot, and installed the system from the disk. Now everything works fine. Apparently, initially it was necessary to do so :)