pman does not build module mupdf

Arch based Porteus community project
Post Reply
M. Eerie
Black ninja
Black ninja
Posts: 80
Joined: 31 Aug 2017, 21:18
Distribution: APorteus BUDGIE x64

pman does not build module mupdf

Post#1 by M. Eerie » 01 Feb 2018, 17:01

So, I've put all this stuff in a pendrive and booted fine.
Then
1.- setup-pman
2.- pman -S mupdf
and I can see the package downloaded at /var/cache/pacman/pkg/mupdf-1.12.0-1-x86_64.pkg.tar.xz
but it is not converted to .xzm module.

I've been trying with other packages as well with same results.
Then, I've manually converted the packages to modules:
cp /var/cache/pacman/pkg/*.xz /home/guest/XYZ
and
dir2xzm /home/guest/XYZ mupdf-1.12.0-1-x86_64.xzm

(at this stage, activating the module works and I can run mupdf without a problem). Then
cp mupdf-1.12.0-1-x86_64.xzm --> /mnt/sdb1/porteus/modules

and reboot. But then neither mupdf, mpv (...) module I've built and put on the modules folder actually works.

However, I can see the downloaded packages (*.xz) located at / in the Filesystem

What's going on??

(will add some screeshots later)

:%)

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 1409
Joined: 20 Mar 2012, 03:42
Distribution: 4.0-64bit all-DE+more
Location: australia
Contact:

pman does not build module

Post#2 by ncmprhnsbl » 01 Feb 2018, 21:58

M. Eerie wrote:
01 Feb 2018, 17:01
and I can see the package downloaded at /var/cache/pacman/pkg/mupdf-1.12.0-1-x86_64.pkg.tar.xz
but it is not converted to .xzm module.
i don't use pman much(i have known it to fail at times)the, but did you check /tmp for the module?
M. Eerie wrote:
01 Feb 2018, 17:01
Then, I've manually converted the packages to modules:
cp /var/cache/pacman/pkg/*.xz /home/guest/XYZ
and
dir2xzm /home/guest/XYZ mupdf-1.12.0-1-x86_64.xzm
all you've done here is make a module with a package in it's root directory, hence:
M. Eerie wrote:
01 Feb 2018, 17:01
However, I can see the downloaded packages (*.xz) located at / in the Filesystem
there are several ways to manually make a module:
eg.
for a downloaded package:

Code: Select all

pkg2xzm /var/cache/pacman/pkg/mupdf-1.12.0-1-x86_64.pkg.tar.xz
for an installed package:

Code: Select all

arc2xzm mupdf
:with pacman:

Code: Select all

mkdir -p /tmp/build/var/lib/pacman/local
cp /var/lib/pacman/local/ALPM_DB /tmp/build/var/lib/pacman/local
pacman -Uddr /tmp/build mupdf-1.12.0-1-x86_64.pkg.tar.xz
rm /tmp/build/var/lib/pacman/local/ALPM_DB 
dir2xzm /tmp/build mupdf-1.12.0-1-x86_64.xzm
(module will be in current working directory)
note: pman makes a module(when it works) by
1. installing to the live system (which is why your package worked to start with)
2. then extracting the installed files to make the module
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

Jack
Contributor
Contributor
Posts: 1514
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 4.0rc4 My LXDE 64 bit
Location: USA

2018 Updated Base Modules

Post#3 by Jack » 02 Feb 2018, 00:40

@M. Eerie,
I built what you posted and here is the output and look at it close. Your might be the same because I use my LXDE desktop.
Here is the setup-pman. When you see this "Would you like to create a module from your settings? [y/n]"y

Code: Select all

[guest@porteus ~]$ su
Password: 
[porteus guest]# setup-pman
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signing key DDB867B92AA789C165EEFA799B729B06A680C281...
  -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
  -> Locally signing key 91FFE0700E80619CEB73235CA88E23E377514E00...
  -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
  -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
==> Importing owner trust values...
==> Disabling revoked keys in keyring...
  -> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
  -> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
  -> Disabling key 40440DC037C05620984379A6761FAD69BA06C6A9...
  -> Disabling key B1F2C889CB2CCB2ADA36D963097D629E437520BD...
  -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
  -> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
  -> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
  -> Disabling key 4FCF887689C41B09506BE8D5F3E1D5C5D30DB0AD...
  -> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
  -> Disabling key 5E7585ADFF106BFFBBA319DC654B877A0864983E...
  -> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
  -> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
  -> Disabling key 8CF934E339CAD8ABF342E822E711306E3C4F88BC...
  -> Disabling key 5696C003B0854206450C8E5BE613C09CB4440678...
  -> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
  -> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
  -> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
  -> Disabling key 34C5D94FE7E7913E86DC427E7FB1A3800C84C0A5...
  -> Disabling key 39F880E50E49A4D11341E8F939E4F17F295AFBF4...
  -> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
  -> Disabling key 44D4A033AC140143927397D47EFD567D4C7EA887...
  -> Disabling key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
==> Updating trust database...
gpg: next trustdb check due at 2018-06-01
==> Appending keys from artix.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signing key 8AC1470E584E6AAB0BBBAC3FED587B6247A4152D...
  -> Locally signing key 2C69BCE8163847BC56401FD2CF18A351C0705F6A...
  -> Locally signing key 664187F32A958D0ED06530067BFAD0C0864DA8E8...
  -> Locally signing key 80E461C30BE40AD3EFB57E18EA690BC73A4F1094...
==> Importing owner trust values...
==> Updating trust database...
gpg: next trustdb check due at 2018-06-01

 Updating database ... 

:: Synchronizing package databases...
 system                                       173.3 KiB   379K/s 00:00 [########################################] 100%
 world                                        475.2 KiB  1327K/s 00:00 [########################################] 100%
 galaxy                                       101.3 KiB  1877K/s 00:00 [########################################] 100%
 extra                                       1629.8 KiB   726K/s 00:02 [########################################] 100%
 community                                      4.1 MiB   309K/s 00:13 [########################################] 100%
 Updating certificates /// 

df: /porteus: No such file or directory
 Changes are not on a real file system. 


 It seems you are not saving your changes. 

Would you like to create a module from your settings? [y/n]y
/tmp
Parallel mksquashfs: Using 2 processors
Creating 4.0 filesystem on /tmp/pacman-settings.xzm, block size 262144.
[=======================================================================================================\] 40/40 100%

Exportable Squashfs 4.0 filesystem, xz compressed, data block size 262144
	compressed data, compressed metadata, compressed fragments, compressed xattrs
	duplicates are removed
Filesystem size 7420.82 Kbytes (7.25 Mbytes)
	98.04% of uncompressed filesystem size (7568.79 Kbytes)
Inode table size 442 bytes (0.43 Kbytes)
	40.70% of uncompressed inode table size (1086 bytes)
Directory table size 550 bytes (0.54 Kbytes)
	72.08% of uncompressed directory table size (763 bytes)
Number of duplicate files found 2
Number of inodes 32
Number of files 16
Number of fragments 2
Number of symbolic links  0
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 5
Number of directories 11
Number of ids (unique uids + gids) 1
Number of uids 1
	root (0)
Number of gids 1
	root (0)

7.3M	/tmp/pacman-settings.xzm

/tmp/pacman-settings.xzm was moved to your modules directory.
This means that changes will persist at next boot.
[porteus guest]# 
Remember to reboot.
Next build pman -S mupdf. When you see this "Proceed with installation? [Y/n]" hit ENTER then when you see this "Would you like to merge them into one module? [y/n]"y and this "Enter a custom module name or hit enter for default:" mupdf-1.12.0-2.xzm

Code: Select all

[guest@porteus ~]$ su
Password: 
[porteus guest]# pman -S mupdf
resolving dependencies...
looking for conflicting packages...

Packages (2) jbig2dec-0.14-1  mupdf-1.12.0-2

Total Download Size:   17.52 MiB
Total Installed Size:  33.83 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 jbig2dec-0.14-1-x86_64                           49.6 KiB   201K/s 00:00 [##########################################] 100%
 mupdf-1.12.0-2-x86_64                            17.5 MiB   260K/s 01:09 [##########################################] 100%
(2/2) checking keys in keyring                                            [##########################################] 100%
(2/2) checking package integrity                                          [##########################################] 100%
(2/2) loading package files                                               [##########################################] 100%
(2/2) checking for file conflicts                                         [##########################################] 100%
(2/2) checking available disk space                                       [##########################################] 100%
:: Processing package changes...
(1/2) installing jbig2dec                                                 [##########################################] 100%
warning: directory permissions differ on /usr/lib/
filesystem: 775  package: 755
(2/2) installing mupdf                                                    [##########################################] 100%
:: Running post-transaction hooks...
(1/1) Updating the desktop file MIME type cache...

 Multiple packages were detected. 

Would you like to merge them into one module? [y/n]y
Enter a custom module name or hit enter for default: mupdf-1.12.0-2.xzm
 Decompressing jbig2dec-0.14-1-x86_64.pkg.tar.xz 
 Stripping jbig2dec-0.14-1-x86_64.pkg.tar.xz 

 Size before strip: 
 212K
 Size after strip: 
 188K

 Decompressing mupdf-1.12.0-2-x86_64.pkg.tar.xz 
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
 Stripping mupdf-1.12.0-2-x86_64.pkg.tar.xz 

 Size before strip: 
 34M
 Size after strip: 
 34M

/tmp
Parallel mksquashfs: Using 2 processors
Creating 4.0 filesystem on /tmp/mupdf-1.12.0-2.xzm, block size 262144.
[==========================================================================================================\] 146/146 100%

Exportable Squashfs 4.0 filesystem, xz compressed, data block size 262144
	compressed data, compressed metadata, compressed fragments, compressed xattrs
	duplicates are removed
Filesystem size 22684.32 Kbytes (22.15 Mbytes)
	65.71% of uncompressed filesystem size (34520.30 Kbytes)
Inode table size 722 bytes (0.71 Kbytes)
	47.31% of uncompressed inode table size (1526 bytes)
Directory table size 390 bytes (0.38 Kbytes)
	64.46% of uncompressed directory table size (605 bytes)
Number of duplicate files found 0
Number of inodes 30
Number of files 12
Number of fragments 1
Number of symbolic links  2
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 16
Number of ids (unique uids + gids) 1
Number of uids 1
	root (0)
Number of gids 1
	root (0)

23M	/tmp/mupdf-1.12.0-2.xzm

 Operation completed successfully. 
The following modules were copied to your modules folder:
/mnt/sdb1/porteus/modules

mupdf-1.12.0-2.xzm

Packages were removed from /var/cache/pacman/pkg.

[porteus guest]# 
It should be in your porteus/modules directory. Remember reboot
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

M. Eerie
Black ninja
Black ninja
Posts: 80
Joined: 31 Aug 2017, 21:18
Distribution: APorteus BUDGIE x64

2018 Updated Base Modules

Post#4 by M. Eerie » 02 Feb 2018, 16:02

Ok, thanks very much Jack and ncmprhnsbl

I think I have it all now. Probably I've missed the pkg2xzm command.

Will try again and come with some feedback.

BTW, ncmprhnsbl I've noticed this 003-xfce4-20180128.xzm of yours doesn't have the xfce4-whiskermenu panel plugin. How is that?

Cheers!

Jack
Contributor
Contributor
Posts: 1514
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 4.0rc4 My LXDE 64 bit
Location: USA

2018 Updated Base Modules

Post#5 by Jack » 02 Feb 2018, 16:26

@M. Eerie
Probably I've missed the pkg2xzm command.
If you do it my way you won't need pkg2xzm.
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

M. Eerie
Black ninja
Black ninja
Posts: 80
Joined: 31 Aug 2017, 21:18
Distribution: APorteus BUDGIE x64

2018 Updated Base Modules

Post#6 by M. Eerie » 03 Feb 2018, 13:51

@ncmprhnsbl,
@Jack
Jack wrote:
02 Feb 2018, 16:26
If you do it my way you won't need pkg2xzm.
Image


Working now :friends:

Thank you all

User avatar
francois
Contributor
Contributor
Posts: 5330
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

pman does not build module mupdf

Post#7 by francois » 03 Feb 2018, 14:33

To try to answer your first post interrogation. It happens that the module will end into the /tmp folder instead of the /porteus/modules one.
Prendre son temps, profiter de celui qui passe.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 1409
Joined: 20 Mar 2012, 03:42
Distribution: 4.0-64bit all-DE+more
Location: australia
Contact:

pman does not build module mupdf

Post#8 by ncmprhnsbl » 05 Feb 2018, 04:42

after investigating this, i have found pman is not building modules for me either .. (using xfce or my own openbox module)
output:

Code: Select all

[porteus guest]# pman -S epdfview
No such file or directory: /tmp/pman.APF4rT/package.out
resolving dependencies...
looking for conflicting packages...

Packages (3) poppler-0.61.1-1  poppler-glib-0.61.1-1  epdfview-0.1.8-8

Total Installed Size:  6.87 MiB

:: Proceed with installation? [Y/n] 
(3/3) checking keys in keyring                     [######################] 100%
(3/3) checking package integrity                   [######################] 100%
(3/3) loading package files                        [######################] 100%
(3/3) checking for file conflicts                  [######################] 100%
(3/3) checking available disk space                [######################] 100%
:: Processing package changes...
(1/3) installing poppler                           [######################] 100%
Optional dependencies for poppler
    poppler-data: encoding data to display PDF documents containing CJK
    characters
(2/3) installing poppler-glib                      [######################] 100%
(3/3) installing epdfview                          [######################] 100%
:: Running post-transaction hooks...
(1/2) Updating icon theme caches...
(2/2) Updating the desktop file MIME type cache...
this line is possibly a clue:

Code: Select all

No such file or directory: /tmp/pman.APF4rT/package.out
why this file isn't being created, so far, is a mystery..
Jack wrote:
02 Feb 2018, 00:40
I built what you posted and here is the output and look at it close. Your might be the same because I use my LXDE desktop.
@Jack, are you using the latest base modules?
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 1409
Joined: 20 Mar 2012, 03:42
Distribution: 4.0-64bit all-DE+more
Location: australia
Contact:

pman does not build module mupdf

Post#9 by ncmprhnsbl » 05 Feb 2018, 05:24

ncmprhnsbl wrote:
05 Feb 2018, 04:42

Code: Select all

No such file or directory: /tmp/pman.APF4rT/package.out
why this file isn't being created, so far, is a mystery..
after some more investigation, it appears that after the latest update to inotify-tools,
inotifywait is unable to create the output file: package.out (that it needs to write to)
my solution:
add to /usr/local/bin/pman line 396:

Code: Select all

touch $WRK/package.out
will be included in next update..
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

Jack
Contributor
Contributor
Posts: 1514
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 4.0rc4 My LXDE 64 bit
Location: USA

pman does not build module mupdf

Post#10 by Jack » 05 Feb 2018, 13:58

Code: Select all

[guest@porteus ~]$ su
Password: 
[porteus guest]# pman -S mupdf
resolving dependencies...
When you use pman you can't login as guest you have to login as su to work.
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 1409
Joined: 20 Mar 2012, 03:42
Distribution: 4.0-64bit all-DE+more
Location: australia
Contact:

pman does not build module mupdf

Post#11 by ncmprhnsbl » 05 Feb 2018, 22:28

:) well aware of that..
# means root
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
francois
Contributor
Contributor
Posts: 5330
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

pman does not build module mupdf

Post#12 by francois » 06 Feb 2018, 03:00

Is this an issue only with the latest base module or of previous also?
Prendre son temps, profiter de celui qui passe.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 1409
Joined: 20 Mar 2012, 03:42
Distribution: 4.0-64bit all-DE+more
Location: australia
Contact:

pman does not build module mupdf

Post#13 by ncmprhnsbl » 06 Feb 2018, 21:55

latest afaik
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

Post Reply