Simple Package Manager for Debian type

Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
User avatar
francois
Contributor
Contributor
Posts: 5116
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Simple Package Manager for Debian type

Post#31 by francois » 19 May 2014, 20:36

Excuse me.
Now I can not test 'spm DEB' for 64bit because I haven't a 64bit PC on April and May.


No problem at all for me as on 64bit I can work with 32bit porteus 3.0. From now on I will work exclusively with 32bit. :)

I have been testing the digikam program for photography. There is a great lot of dependencies here. It seems to break porteus installation,porteus will not log into X. The error message is:
unable to load debiabXXX module corrupte module for each module of digikam.

What can we do about that?
Voltaire: Le mieux est l'ennemi du bien.

neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Re: Simple Package Manager for Debian type

Post#32 by neko » 26 May 2014, 08:53

@francois
Thank you for a problem report.

Q: What can we do about that?

A: I'm sorry, there is no direct answer.

I tested 'spmDebian' for 'digikam'.

And then,
[ 'spmDebian' is updated.]
======================================================
spmDebian-14.05.23-noarch-1.xzm
http://www.mediafire.com/download/u61eh ... arch-1.xzm
md5sum: 2dca27e8fd6f3253ea72a38fe2dea047 spmDebian-14.05.23-noarch-1.xzm

1. A bug is fixed.
the 'mount/unmount' pair, that are used by checking on 'ldd' command, are set correctly.
(delete an unmount without a paired mount).

2. enhance 'module' manipulations.
(1) old: 'Convert DEB to EXM' was specified by 'DEB' file name.
new: It is specified by directory name that has 'DEB' files.
(2) The process, that merge all of the dependent libraries into one single library module containing all dependencies,
had 2 steps.
First step: get dependencies depending on the package information.
Second step: get dependencies depending on 'ldd' command.
Now this first step is skipped.

3. 'exeDebian' is offered.
It is a shell script and has the following sentence in the head of it.
# This wrapper is for the applications that need shared libraries of the debian directories;
# /lib/i386-linux-gnu:/usr/lib/i386-linux-gnu:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:
# /lib32:/usr/lib32
# [ how to use ]
# application X is in /Path
# # cd /Path
# # mv X X-bin
# # ln -sf /usr/bin/exeDebian X

4. delete '/etc/rc.d/rc.local' that sets the debian shared libraries path.
The '/etc/rc.d/rc.local' is system wide resource.
Therefor it is better not to be used, so the wrapper will be used.


[Result of test new spmDebian]
======================================================
I modified /usr/bin/xxx before run.
-------------------------------------
# cd /usr/bin
# mv digikam digikam-bin
# ln -sf exeDebian digikam
# mv cleanup_digikamdb cleanup_digikamdb-bin
# ln -sf exeDebian cleanup_digikamdb
# mv digitaglinktree digitaglinktree-bin
# ln -sf exeDebian digitaglinktree
-------------------------------------
tested UBUNTU14.04 DEBs
http://www.mediafire.com/download/akm83 ... ntudeb.tar
3068aa527db16a89ab2eb2e1712d65b0 ubuntudeb.tar

1.64bit-kde: Debian7.5
merge completed.
lib4digikam_2.6.0-1+b2_amd64.xzm size is 8478720
RUN result is Log of 1.

2.64bit-kde: sid
merge completed.
lib4digikam_4.0.0-1_amd64.xzm size is 7487488
RUN result
guest@porteus:~$ export LANG=C;digikam
/usr/bin/digikam-bin: /lib64/liblzma.so.5: no version information available (required by /usr/lib/x86_64-linux-gnu/libtiff.so.5)
/usr/bin/digikam-bin: symbol lookup error: /usr/lib/digikam/libdigikamcore.so.4.0.0: undefined symbol: _ZTVN12QtConcurrent9ExceptionE

3.64bit-kde: Debian7.5(libtasn1-3_2.13-2_amd64.xzm) + UBUNTU14.04 DEBs (Convert & Merge)
merge completed.
lib4digikam_4%3a3.5.0-0ubuntu10_amd64.xzm size is 9445376
RUN result is Log of 3.

---------------------------------------
log file
http://www.mediafire.com/view/v51vqt9yy ... log1-2.txt

neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Re: Simple Package Manager for Debian type

Post#33 by neko » 26 May 2014, 10:33

continue
[Result of test new spmDebian]

4.64bit-lxde: Debian7.5
merge completed.
lib4digikam_2.6.0-1+b2_amd64.xzm size is 28286976
RUN result
(message box)
Run-time Qt4 SQLite or MySQL database plugin is not available - please install it.
There is no database plugin installed on your computer.

(terminal)
Log of 4.

5.64bit-xfce: Debian7.5
merge completed.
lib4digikam_2.6.0-1+b2_amd64.xzm size is 28286976
RUN result
(message box)
Run-time Qt4 SQLite or MySQL database plugin is not available - please install it.
There is no database plugin installed on your computer.

(terminal)
Log of 5.

6. 64bit-mate: Debian7.5(libtasn1-3_2.13-2_amd64.xzm) + UBUNTU14.04 DEBs
merge completed.
lib4digikam_4%3a3.5.0-0ubuntu10_amd64.xzm size is 35688448.
RUN result
(message box)
Run-time Qt4 SQLite or MySQL database plugin is not available - please install it.
There is no database plugin installed on your computer.

(terminal)
Log of 6.

7. 64bit-razor: Debian7.5
merge completed.
lib4digikam_2.6.0-1+b2_amd64.xzm size is 15187968.
RUN result
(message box)
The database has been used with a more recent version of digiKam and has been updated to a database schema which cannot be used with this version. (This means this digiKam version is too old, or the database format is too recent.) Please use the more recent version of digiKam that you used before.

(terminal)
Log of 7.

---------------------------------------
log file
http://www.mediafire.com/view/249e6r91l ... log4-7.txt

Thanks.

User avatar
francois
Contributor
Contributor
Posts: 5116
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Simple Package Manager for Debian type

Post#34 by francois » 28 May 2014, 11:08

Hi neko.

Could you summarize simply the result of the above two links. What works now?
Voltaire: Le mieux est l'ennemi du bien.

neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Re: Simple Package Manager for Debian type

Post#35 by neko » 28 May 2014, 12:23

@francois

Summary of the test result is that
'digikam' did run only in kde window managers.

What works now is that
New spmDebian merges all libraries that are needed by 'digikam' in every window managers.

Thanks

User avatar
francois
Contributor
Contributor
Posts: 5116
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Simple Package Manager for Debian type

Post#36 by francois » 28 May 2014, 17:16

Thus new spm deb should provide a functional digikam program under kde, with what database?
Voltaire: Le mieux est l'ennemi du bien.

User avatar
francois
Contributor
Contributor
Posts: 5116
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Simple Package Manager for Debian type

Post#37 by francois » 19 Jul 2014, 11:24

Hello neko. I have tried to install kalarm on my 32bit porteus installation. It would not work.
Thanks.
Voltaire: Le mieux est l'ennemi du bien.

neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Re: Simple Package Manager for Debian type

Post#38 by neko » 21 Jul 2014, 09:17

@francois
Excuse me. It was long-term absence rude.

[ 'spmDebian' is updated.]
======================================================
spmDebian-14.07.21-noarch-1.xzm
http://www.mediafire.com/download/rdeoc ... arch-1.xzm
md5sum: d0f2648ec653c94cbd31eae80792a95c spmDebian-14.07.21-noarch-1.xzm

1.Improvement
Debian library paths are set for executables in .xzm module.

(1)Debian library paths
For 32 bit executables,
These paths (/lib/i386-linux-gnu,/usr/lib/i386-linux-gnu) are refered.
For 64 bit executables,
These paths (/lib32,/lib/x86_64-linux-gnu,/usr/lib32,/usr/lib/x86_64-linux-gnu) are refered.

(2)executables in .xzm module
Executables that exist in (bin,sbin,usr/bin,usr/sbin) will be set.
If there are executables that need 'Debian library paths' but are not in those directories,
they must be set manually.

(3)example
kalarm_4.4.11.1+l10n-3+b1_i386.xzm is gotten by 'spmDebian' upon 32bit Porteus KDE & Debian7.6.

old:spmDebian-14.05.23-noarch-1.xzm
% lsxzm kalarm_4.4.11.1+l10n-3+b1_i386.xzm
/usr
/usr/bin
/usr/bin/kalarm
/usr/bin/kalarmautostart
/usr/lib
....
*note) 'Debian library paths' were manually set. The run was OK.

new:spmDebian-14.07.21-noarch-1.xzm
% lsxzm kalarm_4.4.11.1+l10n-3+b1_i386.xzm
/usr
/usr/bin
/usr/bin/kalarm
/usr/bin/kalarm-bin
/usr/bin/kalarmautostart
/usr/bin/kalarmautostart-bin
/usr/lib
...

kalarm-bin,kalarmautostart-bin are original kalarm,kalarmautostart.
kalarm,kalarmautostart are copies of /usr/bin/exeDebian.

======================================================
['spmDebian' and 'Debian library paths' issue history]
1.manually set
==>refer:'17 Mar 2014, 13:36'
viewtopic.php?f=75&t=3216#p22824

One of issues is 'ldd path lack'.
The lacked paths must be set manually.

2.The paths will be set by using global resource.
==>refer:'19 Mar 2014, 05:40'
viewtopic.php?f=75&t=3216#p22889

A patch will be inserted in order to set 'libpath for debian'.
This patch run at booting in '/etc/rc.d'.
So, spmDebian must have been already activated at booting.

==>refer:'19 Mar 2014, 07:57'
viewtopic.php?f=75&t=3216#p22890

"2. additional function
(1) A patch is inserted in order to set 'libpath for debian'.
This patch run at booting in '/etc/rc.d'.
So, spmDebian must have been already activated at booting."

3.The paths will be set manually by using exeDebian tool shell.
==>refer:'26 May 2014, 09:53'
viewtopic.php?f=75&t=3216&start=30#p25226

"3. 'exeDebian' is offered.
4. delete '/etc/rc.d/rc.local' that sets the debian shared libraries path."

Thanks.

neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Re: Simple Package Manager for Debian type

Post#39 by neko » 28 Jan 2015, 14:37

[ 'spmDebian' is updated.]
======================================================
spmDebian-15.01.28-noarch-1.xzm
http://www.mediafire.com/download/ezmab ... arch-1.xzm
md5sum: 19e6d96f30452eac90696dde3ae379b7 spmDebian-15.01.28-noarch-1.xzm

1. A bug is fixed.
[ bug ]
Some packages are skipped to be analyzed dependency.

[ cause ]
A package dependency analyzing with 'ldd' command should be tested in the real environment.
But if a library in a package is same name library that is currently used by some process,
the package mounted on the real root space cannot be unmounted.

Therefor spmDebian mounts library packages on a temporary space.
And it mounts other packages on the real root (/) space.
spmDebian decides that first 3 characters of a package name being 'lib' is a library package.
(For example, 'glibc.xzm' is not a library package)

Some not-library packages cannot be unmounted on the reason of the being currently used.
From the cause of this, the next "packages dependency analyzing" not be continued.

[ fix ]
All packages are mounted on a temporary space.
======================================================

Thanks.

User avatar
francois
Contributor
Contributor
Posts: 5116
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Simple Package Manager for Debian type

Post#40 by francois » 29 Jan 2015, 18:27

Thanks neko. I am happy to read that you continue the amelioration of SPM for debian. :)
Voltaire: Le mieux est l'ennemi du bien.

neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Re: Simple Package Manager for Debian type

Post#41 by neko » 30 Jan 2015, 03:59

@francois and spmDebian users
Excuse me.
The new version makes users update its database.

If a new version name were spmDebian-14.07.21-noarch-2.xzm, its updating database would not be performed.
But a new version name is spmDebian-15.01.28-noarch-1.xzm.
Old database ( XXXX-spm-14.07.21-i386-1.xzm and INFO.LIST-14.07.21 ) will be abandoned
and new database ( XXXX-spm-15.01.28-i386-1.xzm and INFO.LIST-15.01.28 ) will be created.

note1) 'XXXX' is a debian version name.
Example: Debian7.8-spm-15.01.28-i386-1.xzm

note2) Old database should be removed manually.
% su
# rm *-spm-14.07.21-i386-1.xzm INFO.LIST-14.07.21

Thanks.

User avatar
francois
Contributor
Contributor
Posts: 5116
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Simple Package Manager for Debian type

Post#42 by francois » 31 Jan 2015, 22:19

A very general question for you neko:
With the experience that you have developed with SPM debian type, what would be some general restrictions to packages built from debian sources? For example, do you advise always using slackware packages first or do you think that SPM debian type could do a good job on most .deb packages? At some times could these packages damage the porteus installation? Do you advise to install small and medium packages and put aside more complex packages? What debian database do you prefer to build your own packages? For specific packages asking to modify /etc/apt/sources.list is there a possibility?

As an example I submit kodi multimedia center for debian, it encompasses some of these interrogations of mine:
https://people.debian.org/~rbalint/ppa/xbmc-ffmpeg/
Voltaire: Le mieux est l'ennemi du bien.

neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

Re: Simple Package Manager for Debian type

Post#43 by neko » 01 Feb 2015, 07:57

@francois

1. what would be some general restrictions to packages built from debian sources?

spmDebian cannot analyze the dependencies of script texts.

If the (debian,ubuntu,etc.,) system dependency of packages is strong,
it might be difficult to port these package.
There might be many kind dependencies.
My skill cannot explain these dependencies.
Case by case, I would try porting.

For example.
There are library reference paths in a debian type system.
(32 bit)
/lib/i386-linux-gnu:/usr/lib/i386-linux-gnu
(64 bit)
/lib32:/lib/x86_64-linux-gnu:/usr/lib32:/usr/lib/x86_64-linux-gnu


2. do you advise always using slackware packages first?

Yes, I do.
The reason is that slackware packages are just fit to Porteus.


3. do you think that SPM debian type could do a good job on most .deb packages?

Case by case.
From the view point of an easiness,
it could do a good job simply.
From the view point of an completeness,
it could not do a good job enough.
Sometimes it needs manual operations and human skills.

For example 'xbcm'.
It is difficult for spmDebian to get full dependency packages of 'xbcm'.
Because spmDebian uses the 'ldd' command method in order to analyze dependencies,
it cannot analyze the dependencies of script texts.
For script case, it could be used only to assist manual operations.
For this purpose, first it downloads the packages that are described in the target's package information
even if these packages are not used to create a merged library for the target package.


4. At some times could these packages damage the porteus installation?

Yes, those could do.
Especially the case that the libraries of those are racing against slackware libraries.


5. Do you advise to install small and medium packages and put aside more complex packages?

Case by case.
For example.
The 'adobe flash player' library is included in a web browser package, or is not.
I cannot say which is better.
A flash and a web are used together.
But updates will be done separately.


6. What debian database do you prefer to build your own packages?

'Debian7.8' is used.


7. For specific packages asking to modify /etc/apt/sources.list is there a possibility?

No, there is not.
That case is beyond 'Simple' (and my skill).


Thanks.

User avatar
francois
Contributor
Contributor
Posts: 5116
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Simple Package Manager for Debian type

Post#44 by francois » 04 Feb 2015, 22:58

Thanks for the explanations. It would be really nice that more people use your SPM debian type! :)
Voltaire: Le mieux est l'ennemi du bien.

User avatar
francois
Contributor
Contributor
Posts: 5116
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Simple Package Manager for Debian type

Post#45 by francois » 10 Sep 2015, 02:36

@neko:
Is Simple Package Manager for Debian type is still an active project?
Voltaire: Le mieux est l'ennemi du bien.

Post Reply