SliTaz Forum

rolling get-LibreOffice broken - ugly (?) fix

(7 posts) (2 voices)

• Started 11 years ago by ernia
• Latest reply from ernia
• This topic is resolved

Tags:

No tags yet.

1. 

   ernia
   

   offline

   Member

   Running get-LibreOffice lead /usr/bin/libreoffice3.6 to be a broken link to /opt/libreoffice3.6/program/soffice, so the program looks installed but does not start .
   

   root@slitaz:/home/tux6 ls -la /usr/bin/libreoffice3.6
   lrwxrwxrwx    1 root     root            35 Jan  5 22:49 /usr/bin/libreoffice3.6 -> /opt/libreoffice3.6/program/soffice

   The trouble is in the bin variable definition at line 167: bin=$(ls $PACKAGE-$VERSION/fs/usr/bin/libreoffice???)
   I don't know the reason why but the ls command does not seems to catch libreoffice3.6 when running inside the script while it works well from sakura.
   

   Extracting files (this may take a while): (found v3.6.4.3)           [ OK ]
   ............................................................         [ OK ]
   Preparing package... ls: LibreOffice-3.6.4/fs/usr/bin/libreoffice3.6: No such file or directory
   
   Command line: readlink 
   
   BusyBox v1.20.2 (2012-12-21 21:52:58 CET) multi-call binary.
   
   Usage: readlink [-fnv] FILE
   
   Display the value of a symlink
   
   	-f	Canonicalize by following all symlinks
   	-n	Don't add newline
   	-v	Verbose
   
   Command line: ln -s 
   
   BusyBox v1.20.2 (2012-12-21 21:52:58 CET) multi-call binary.
   
   Usage: ln [OPTIONS] TARGET... LINK|DIR
   
   Create a link LINK or DIR/TARGET to the specified TARGET(s)
   
   	-s	Make symlinks instead of hardlinks
   	-f	Remove existing destinations
   	-n	Don't dereference symlinks - treat like normal file
   	-b	Make a backup of the target (if exists) before link operation
   	-S suf	Use suffix instead of ~ when making backup files
   
                                                                        [ OK ]

   I brutally fixed it changing the row with
   

   bin=$(ls $PACKAGE-$VERSION/fs/usr/bin/*printeradmin | sed 's/-printeradmin//')

   also seems that tazpkg remove LibreOffice leave /usr/lib/libreoffice/libreoffice3.6

   Installation of: LibreOffice
   =====================================================================================================================================================================================================================
   Copying LibreOffice...                                                                                                                                                                                    [ Done ]
   Extracting LibreOffice...                                                                                                                                                                                 [ Done ]
   Extracting the pseudo fs...                                                                                                                                                                               [ Done ]
   Installing LibreOffice...                                                                                                                                                                                 [ Done ]
   Removing all tmp files...                                                                                                                                                                                 [ Done ]
   ln: /usr/lib/libreoffice/libreoffice3.6: File exists
   =====================================================================================================================================================================================================================
   LibreOffice (3.6.4) is installed.

   Posted 11 years ago #
2. 

   ernia
   

   offline

   Member

   rechecking i did use bin=$(ls LibreOffice-3.6.4/fs/usr/bin/*printeradmin | sed 's/-printeradmin//') , so the problem could be in $VERSION ...
   i have no time now, will recheck next days

   PS it does not seem to be a $VERSION problem, seems to be 3.6.4 as it should be.

   Posted 11 years ago #
3. 

   ernia
   

   offline

   Member

   get-LibreOffice script is identical in 4.0 and rolling, works properly in 4.0 and does not work properly in rolling.
   the problem seems to be related to busybox.
   in my brand new rolling install i downgraded busybox from 1.20.2 to 1.18.4 installing the 4.0 package, then tazpkg get-install get-Libre-Office and #get-LibreOffice: all worked well and i ended up with a working package.
   upgrading again to 1.20.2 makes the script raise the same error and makes it produce an unusable package.
   i think that someone more skilled than me should try to debug this.

   Posted 11 years ago #
4. 

   ernia
   

   offline

   Member

   @Bellard
   i've tried your fix http://hg.slitaz.org/wok/rev/24d193656599 and it does not seem to work.
   reading more carefully the output of the error was
   ls: LibreOffice-3.6.4/fs/usr/bin/libreoffice3.6: No such file or directory
   it seems that 3.6 got catched but the file does not exist, so i made these tests:
   

   root@slitaz:/tmp/LibreOffice.5524/LibO_3.6.4.3_Linux_x86_install-rpm_en-US/RPMS# ls -l LibreOffice-3.6.4/fs/usr/b
   in/libreoffice3.6
   lrwxrwxrwx    1 root     root            35 Jan  8 10:02 LibreOffice-3.6.4/fs/usr/bin/libreoffice3.6 -> /opt/librroot@slitaz:/tmp/LibreOffice.5524/LibO_3.6.4.3_Linux_x86_install-rpm_en-US/RPMS# ls  LibreOffice-3.6.4/fs/usr/bin
   /libreoffice3.6
   root@slitaz:/tmp/LibreOffice.5524/LibO_3.6.4.3_Linux_x86_install-rpm_en-US/RPMS# ls -lH LibreOffice-3.6.4/fs/usr/
   bin/libreoffice3.6
   ls: LibreOffice-3.6.4/fs/usr/bin/libreoffice3.6: No such file or directory
   root@slitaz:/tmp/LibreOffice.5524/LibO_3.6.4.3_Linux_x86_install-rpm_en-US/RPMS#

   it seems like busybox's ls without options follows links, like with -H option.
   being libreoffice3.6 a broken link it outputs ls: LibreOffice-3.6.4/fs/usr/bin/libreoffice3.6: No such file or directory
   i think it's a busybox bug and it could influence the whole distro

   PS the output of commands is a little bit messed up because of the long path, try ls -l , ls -lH and ls

   Posted 11 years ago #
5. 

   ernia
   

   offline

   Member

   tested with shorter path:
   

   tux@slitaz:~$ touch target
   tux@slitaz:~$ ln -s target symlink
   tux@slitaz:~$ ls -l symlink
   lrwxrwxrwx    1 tux      tux              6 Jan  8 10:56 symlink -> target
   tux@slitaz:~$ ls -lH symlink
   -rw-r--r--    1 tux      tux              0 Jan  8 10:55 symlink
   tux@slitaz:~$ ls -l symlink
   lrwxrwxrwx    1 tux      tux              6 Jan  8 10:56 symlink -> target
   tux@slitaz:~$ rm target
   tux@slitaz:~$ ls -l symlink
   lrwxrwxrwx    1 tux      tux              6 Jan  8 10:56 symlink -> target
   tux@slitaz:~$ ls -lH symlink
   ls: symlink: No such file or directory
   tux@slitaz:~$ ls symlink
   ls: symlink: No such file or directory
   tux@slitaz:~$

   it works this way only when link is broken.

   PS it works always this way, too much tests...

   Posted 11 years ago #
6. 

   Bellard
   

   offline

   Key Master

   Try http://hg.slitaz.org/wok/raw-file/bab69144211b/get-LibreOffice/stuff/get-LibreOffice please.

   Posted 11 years ago #
7. 

   ernia
   

   offline

   Member

   it's ok, thanks for your time.
   should busybox checking target link be considered a bug or a feature?
   standard ls doesn't seem to do that.

   Posted 11 years ago #

RSS feed for this topic

Reply

You must log in to post.