(Slack) Attitude : New binary package mangement tool for Slackware

linuxxer · 05-01-2020, 03:13 AM

Slackers,

Here is an update, please check (Slack) Attitude.

@jheengut, @bassmadrigal
Thanks for the suggestions.

Please check...

linuxxer · 06-22-2020, 11:26 PM

Slackers,

Now (Slack) Attitude is rename to Packtools.

Command attitude rename to packtool.

Please check.

Thanks

DaBrze · 07-09-2020, 10:55 AM

Quote:

Originally Posted by linuxxer

Slackers,

Now (Slack) Attitude is rename to Packtools.

Command attitude rename to packtool.

Please check.

Thanks

Look in the /etc/packtools/triggers directory. In the script files there are old $ATTITUDE_LIBEXECDIR vars. Should be exchanged by $PACKTOOLS_LIBEXECDIR I hope.

linuxxer · 07-09-2020, 11:13 PM

Quote:

Originally Posted by DaBrze

Look in the /etc/packtools/triggers directory. In the script files there are old $ATTITUDE_LIBEXECDIR vars. Should be exchanged by $PACKTOOLS_LIBEXECDIR I hope.

Thanks for reporting the bug. I will check and update.

linuxxer · 07-10-2020, 09:57 AM

Quote:

Originally Posted by DaBrze

Look in the /etc/packtools/triggers directory. In the script files there are old $ATTITUDE_LIBEXECDIR vars. Should be exchanged by $PACKTOOLS_LIBEXECDIR I hope.

Changes are done. Please check.

Can't avoid the silly mistakes.

Thanks

DaBrze · 08-28-2020, 03:43 AM

Today I made deep test of packtool (1.0.0a05) to update my qemu slackware64-current system including the kernel.

The steps are as follow:

1) # packtool update - OK.
2) # packtool upgrade-all - All packages have been upgraded, new kernel-generic, kernel-huge, kernel-modules and kernel-source were installed in parallel to the old as expected.
3) # packtool trigger make-initrd - OK
4) # packtool trigger grub-mkconfig - OK
5) The system has successfully rebooted into the new kernel - OK.
6) The system cleaning - failed.

See my steps below.

Quote:

# root@slack64-current:~# packtool clean-system

Nothing to do... Exiting

but old kernel is still installed:

Quote:

# root@slack64-current:~# ls /var/lib/pkgtools/packages/*kernel*5.4*
/var/lib/pkgtools/packages/kernel-generic-5.4.59-x86_64-1
/var/lib/pkgtools/packages/kernel-generic-5.4.61-x86_64-1
/var/lib/pkgtools/packages/kernel-headers-5.4.61-x86-1
/var/lib/pkgtools/packages/kernel-huge-5.4.59-x86_64-1
/var/lib/pkgtools/packages/kernel-huge-5.4.61-x86_64-1
/var/lib/pkgtools/packages/kernel-modules-5.4.59-x86_64-1
/var/lib/pkgtools/packages/kernel-modules-5.4.61-x86_64-1
/var/lib/pkgtools/packages/kernel-source-5.4.59-noarch-1
/var/lib/pkgtools/packages/kernel-source-5.4.61-noarch-1

'packtool' doesn't see it:

Quote:

# root@slack64-current:~# cat /var/lib/packtools/PACKAGES.TXT | grep 5.4 | sed -n '/txz/p' | grep kernel
PACKAGE NAME: kernel-generic-5.4.61-x86_64-1.txz
PACKAGE NAME: kernel-headers-5.4.61-x86-1.txz
PACKAGE NAME: kernel-huge-5.4.61-x86_64-1.txz
PACKAGE NAME: kernel-modules-5.4.61-x86_64-1.txz
PACKAGE NAME: kernel-source-5.4.61-noarch-1.txz

so, 'packtool remove kernel-source' wants to remove the new kernel, unfortunately.

Removing the content of the /var/lib/packtools/ and rebuilding it with 'packtool update' didn't help.

Finally slackman removed old kernel:

Quote:

# root@slack64-current:~# slackman --remove /var/lib/pkgtools/packages/kernel-source-5.4.59-noarch-1
Total 1136 packages are installed, which provides 431344 files in 34101 directories.

Remove : kernel-source-5.4.59-noarch-1

but it didn't delete the empty, unneeded directories:

Quote:

# root@slack64-current:~# ls -ali /usr/src/
total 16
131129 drwxr-xr-x 4 root root 4096 sie 28 08:05 ./
131076 drwxr-xr-x 17 root root 4096 sie 25 19:32 ../
131166 lrwxrwxrwx 1 root root 12 sie 28 08:05 linux -> linux-5.4.61/
248501 drwxr-xr-x 7 root root 4096 sie 28 09:48 linux-5.4.59/
221268 drwxr-xr-x 24 root root 4096 sie 26 21:10 linux-5.4.61/

# root@slack64-current:~# ls -ali /usr/src/linux-5.4.59/
total 28
248501 drwxr-xr-x 7 root root 4096 Aug 28 09:48 ./
131129 drwxr-xr-x 4 root root 4096 Aug 28 08:05 ../
248506 drwxr-xr-x 2 root root 4096 Aug 28 09:48 Documentation/
255844 drwxr-xr-x 4 root root 4096 Aug 28 09:48 arch/
483997 drwxr-xr-x 3 root root 4096 Aug 28 09:48 include/
508357 drwxr-xr-x 3 root root 4096 Aug 28 09:48 scripts/
508573 drwxr-xr-x 3 root root 4096 Aug 28 09:48 tools/

My conclusion.

The 'packtool/packman' is handly tool, follows the native pkgtools rules, quite easy with operating, especially with handling the system check/info/upgrade. But it still needs some improvements with the system cleaning.

linuxxer · 08-31-2020, 01:56 AM

@DaBrze,

Thanks for trying the tool and reporting the issue.

Code:

packtool clean-system

Packtool is designed such that it must remove all obsolete packages except the kernel-packages.

Currently, If user wants to remove kernel packages he must use slackman tool. And provide complete package name as argument.
Slackman is designed to handle kernel packages properly. But Packtool lacks this functionality. In the next release I will implement it into Packtool.

While deleting the packages, slackman only remove files that are provided by the package. Nothing more than this.
In case of kernel packages it does the same. To remove extra files manual efforts are required like scripting.
Or In future I will add option to handle these kernel files.

walecha · 09-03-2020, 07:42 AM

Quote:

Originally Posted by linuxxer

My attitude repolist
NAME=slackware
IDNUM=431940
DESC="Slackware Official Repository"
SOURCE=ftp://krishna.linuxxlab.org/slackware/slackware64-14.2 patches slackware64 extra testing
ARCH=x86_64
TAG=_slack
PRIORITY=99
CHECKGPG=on
CHECKMD5=on

NAME=slackware.x86
IDNUM=429434
DESC="Slackware Official Repository"
SOURCE=ftp://krishna.linuxxlab.org/slackware/slackware-14.2 patches slackware extra testing
ARCH=x86
TAG=_slack
PRIORITY=98
CHECKGPG=on
CHECKMD5=on

== snip ==

Does packtools support multiple source files or must it be a single file? For example /etc/sources/repo_A.cfg /etc/sources/repo_B.cfg.

Is there a way to add/change sources without having to use some text editor?

walecha · 09-03-2020, 09:32 AM

Packtools indeed support multiple configuration files. Please ignore my first question.

Tested packtools in my multilib system, this is what I got:

Code:

## file /etc/packtools/sources/multilib.cfg
NAME=multilib
IDNUM=5649
DESC="Alien Multilib"
SOURCE=http://192.168.1.15/ftp/alien/multilib current
CHANGELOG=http://192.168.1.15/ftp/alien/multilib
ARCH=x86_64
TAG=alien
PRIORITY=90
CHECKGPG=on
CHECKMD5=on

bash# packtool update     
multilib/ChangeLog.txt - 113KB                                                                                               
multilib/FILELIST.TXT - 880KB                                                                                                
multilib/CHECKSUMS.md5 - 755KB                                                                                               
multilib/current/MANIFEST.bz2 - 214KB                                                                                        
multilib/current/PACKAGES.TXT - 179KB                                                                                        
slackware/ChangeLog.txt - 923KB                                                                                              
Processing update files:
multilib Done.                                                                                                               
Merging databases

bash# packtool info gcc
PACKAGE NAME:  gcc-9.3.0-x86_64-2.txz
PACKAGE LOCATION:  ./slackware64/d
PACKAGE SIZE (compressed):  16796 K
PACKAGE SIZE (uncompressed):  97860 K
PACKAGE DESCRIPTION:
gcc (Base GCC package with C support)

GCC is the GNU Compiler Collection.

This package contains those parts of the compiler collection needed to
compile C code. Other packages add Ada, C++, Fortran, Go,
Objective-C, and BRIG support to the compiler core.

This is what my mirror of alien multilib/current repo looks like:

Code:

http://192.168.1.15/ftp/alien/multilib/current/
[DIR]	debug/	2017-05-07 20:37 	-
[DIR]	slackware64-compat32/	2015-04-22 13:39 	-
[TXT]	CHECKSUMS.md5	2020-08-02 17:39 	159K
[ ]	CHECKSUMS.md5.asc	2020-08-02 17:39 	163
[ ]	CHECKSUMS.md5.gz	2020-08-02 17:39 	37K
[ ]	CHECKSUMS.md5.gz.asc	2020-08-02 17:39 	163
[ ]	compat32-tools-3.9-noarch-16alien.lst	2020-06-24 15:26 	1.5K
[TXT]	compat32-tools-3.9-noarch-16alien.meta	2020-06-24 15:26 	574
[ ]	compat32-tools-3.9-noarch-16alien.tgz	2020-06-24 15:02 	14K
[ ]	compat32-tools-3.9-noarch-16alien.tgz.asc	2020-06-24 15:26 	163
[ ]	compat32-tools-3.9-noarch-16alien.tgz.md5	2020-06-24 15:26 	72
[TXT]	compat32-tools-3.9-noarch-16alien.txt	2020-06-24 15:26 	410
[TXT]	FILELIST.TXT	2020-08-02 17:39 	179K
[ ]	gcc-9.3.0_multilib-x86_64-2alien.lst	2020-04-02 17:24 	87K
[TXT]	gcc-9.3.0_multilib-x86_64-2alien.meta	2020-04-02 17:24 	480
[TXT]	gcc-9.3.0_multilib-x86_64-2alien.txt	2020-04-02 17:24 	310
[ ]	gcc-9.3.0_multilib-x86_64-2alien.txz	2020-04-02 17:00 	17M
[ ]	gcc-9.3.0_multilib-x86_64-2alien.txz.asc
== snip ==

You can see that compat32-tools and gcc multilib suite packages are in multilib/current, but packtools only listed packages inside multilib/current/slackware64-compat32, hence packtools reported my gcc is stock gcc not from multilib. FYI multilib packages using two TAG, alien for compat32-tools, gcc, and glibc, and compat32 for the rest. What tag should be used for multilib repo?

linuxxer · 09-06-2020, 07:26 AM

@walecha

Example Configuration file.

Code:

NAME=alien-compat32
IDNUM=431951
DESC="Eric's multilib compat32 repository"
SOURCE=http://bear.alienbase.nl/mirrors/people/alien/multilib/14.2 slackware64-compat32
ARCH=x86_64
TAG=compat32
PRIORITY=75
CHECKGPG=on
CHECKMD5=on

NAME=alien-multilib
IDNUM=429451
DESC="Eric's multilib repository"
SOURCE=http://bear.alienbase.nl/mirrors/people/alien/multilib 14.2
ARCH=x86_64
TAG=alien
PRIORITY=75
CHECKGPG=on
CHECKMD5=on

Also check PRIORITY value.

Thanks for trying the my tool.

linuxxer · 09-06-2020, 07:29 AM

Slackers,

After changing the priority of package source. (OR) /etc/packtools/preference file.

Please don't forget to run the command.

Quote:

# packtool --force update

Thanks.

jheengut · 09-09-2020, 12:45 PM

this is not working

Code:

git clone "https://git.code.sf.net/p/packtools/git packtools-git"
Cloning into 'git packtools-git'...
fatal: repository 'https://git.code.sf.net/p/packtools/git packtools-git/' not found

svn checkout "https://svn.code.sf.net/p/packtools/svn/ packtools-svn"
svn: E170000: URL 'https://svn.code.sf.net/p/packtools/svn/%20packtools-svn' doesn't exist

from https://sourceforge.net/p/packtools/git/ref/master/

phenixia2003 · 09-10-2020, 02:23 AM

Hello,

Quote:

Originally Posted by jheengut

this is not working

Code:

git clone "https://git.code.sf.net/p/packtools/git packtools-git"
Cloning into 'git packtools-git'...
fatal: repository 'https://git.code.sf.net/p/packtools/git packtools-git/' not found

svn checkout "https://svn.code.sf.net/p/packtools/svn/ packtools-svn"
svn: E170000: URL 'https://svn.code.sf.net/p/packtools/svn/%20packtools-svn' doesn't exist

from https://sourceforge.net/p/packtools/git/ref/master/

This does not work because of the quotes :

Code:

               v                                                      v
$ svn checkout "https://svn.code.sf.net/p/packtools/svn/ packtools-svn"
svn: E170000: URL 'https://svn.code.sf.net/p/packtools/svn/%20packtools-svn' doesn't exist

Remove them and this will work as expected (note that git repository is empty, but not svn) :

Code:

$ git clone https://git.code.sf.net/p/packtools/git packtools-git
Cloning into 'packtools-git'...
warning: You appear to have cloned an empty repository.


$ svn checkout https://svn.code.sf.net/p/packtools/svn/ packtools-svn
A    packtools-svn/packtools-1.0.0
A    packtools-svn/packtools-1.0.0/etc-current
A    packtools-svn/packtools-1.0.0/etc-current/sources
A    packtools-svn/packtools-1.0.0/etc-current/triggers
A    packtools-svn/packtools-1.0.0/etc-stable
A    packtools-svn/packtools-1.0.0/etc-stable/sources
A    packtools-svn/packtools-1.0.0/etc-stable/triggers
A    packtools-svn/packtools-1.0.0/src
A    packtools-svn/packtools-1.0.0/src/triggers
[....]

--
SeB

linuxxer · 09-10-2020, 07:32 AM

Slackers,

Please check now.

Quote:

$ svn checkout https://svn.code.sf.net/p/packtools/svn/ packtools-svn

$ git clone https://git.code.sf.net/p/packtools/git packtools-git

All repositories are updated.

Thanks

linuxxer · 03-19-2021, 12:39 AM

Slackers,

I take a break. But now I decided to continue the project. Not as full time developer. Because I had implemented minimum required functionality.

Now I had added MULTILIB_SUPPORT=disable. So it is required enable this feature in configuration file (/etc/packtools/config).

I like to know whether the package status based functionality is right. So that I can start further development in this direction.

Suggestions are welcome.

Thanks