LSB package not installed - Debian Wheezy 7.6 #468

Closed
black187 opened this Issue Oct 1, 2014 · 7 comments

Comments

Projects
None yet
3 participants
@black187

black187 commented Oct 1, 2014

Hello,

I have a problem with USB restore - error:
Message: The LSB package is not installed

Do i need to install any LSB packages on Debian?

*********************
Version:     Relax-and-Recover 1.16.1 / Git
Validation:  Debian/7.6/i386
Date:        2014-10-01
Features:    LMV, RAID 1
Comment:


*********************

System definition:
                                    ARCH = Linux-i386
                                      OS = GNU/Linux
                        OS_MASTER_VENDOR =
                       OS_MASTER_VERSION =
                   OS_MASTER_VENDOR_ARCH =
                OS_MASTER_VENDOR_VERSION =
           OS_MASTER_VENDOR_VERSION_ARCH =
                               OS_VENDOR = Debian
                              OS_VERSION = 7.6
                          OS_VENDOR_ARCH = Debian/i386
                       OS_VENDOR_VERSION = Debian/7.6
                  OS_VENDOR_VERSION_ARCH = Debian/7.6/i386
Configuration tree:
                         Linux-i386.conf : OK
                          GNU/Linux.conf : OK
                             Debian.conf : missing/empty
                        Debian/i386.conf : missing/empty
                         Debian/7.6.conf : missing/empty
                    Debian/7.6/i386.conf : missing/empty
                               site.conf : missing/empty
                              local.conf : OK
Backup with NETFS
              NETFS_KEEP_OLD_BACKUP_COPY =
                            NETFS_PREFIX = MiSwitchEnterprise
                  BACKUP_INTEGRITY_CHECK =
                         BACKUP_MOUNTCMD =
                          BACKUP_OPTIONS =
                    BACKUP_RSYNC_OPTIONS = --sparse --archive --hard-links --verbose --numeric-ids --stats
                  BACKUP_SELINUX_DISABLE = 1
                             BACKUP_TYPE =
                        BACKUP_UMOUNTCMD =
                              BACKUP_URL = usb:///dev/disk/by-label/REAR-000
Backup program is 'tar':
                             BACKUP_PROG = tar
                     BACKUP_PROG_ARCHIVE = backup
            BACKUP_PROG_COMPRESS_OPTIONS = --gzip
             BACKUP_PROG_COMPRESS_SUFFIX = .gz
               BACKUP_PROG_CRYPT_ENABLED = 0
                   BACKUP_PROG_CRYPT_KEY =
               BACKUP_PROG_CRYPT_OPTIONS = /usr/bin/openssl des3 -salt -k
             BACKUP_PROG_DECRYPT_OPTIONS = /usr/bin/openssl des3 -d -k
                     BACKUP_PROG_EXCLUDE = /tmp/* /dev/shm/* /rear/var/lib/rear/output/*
                     BACKUP_PROG_INCLUDE =
                     BACKUP_PROG_OPTIONS =
      BACKUP_PROG_OPTIONS_CREATE_ARCHIVE =
     BACKUP_PROG_OPTIONS_RESTORE_ARCHIVE =
                      BACKUP_PROG_SUFFIX = .tar
       BACKUP_PROG_WARN_PARTIAL_TRANSFER = 1
Output to USB
                              USB_DEVICE =
                               USB_FILES =
                    USB_RETAIN_BACKUP_NR = 2
                           RESULT_MAILTO =

/rear/usr/share/rear/lib/validated/Debian/7.6/i386.txt
@black187

This comment has been minimized.

Show comment
Hide comment
@black187

black187 Oct 1, 2014

Funny thing is, that the commands:

lsb_release -r -s | tr -s " \t" _
lsb_release -i -s | tr -s " \t" _

printout the correct information (Debian and 7.6) - so the LSB should work.

Only error I see at backup is:

2014-10-01 13:55:09 Including build/default/99_update_os_conf.sh
/usr/src/rear/usr/share/rear/build/default/99_update_os_conf.sh: line 3: /tmp/rear.fD6uwSXFKiYEilv/rootfs//usr/src/rear/etc/rear/os.conf: No such file or directory
/usr/src/rear/usr/share/rear/build/default/99_update_os_conf.sh: line 6: /tmp/rear.fD6uwSXFKiYEilv/rootfs//usr/src/rear/etc/rear/os.conf: No such file or directory

black187 commented Oct 1, 2014

Funny thing is, that the commands:

lsb_release -r -s | tr -s " \t" _
lsb_release -i -s | tr -s " \t" _

printout the correct information (Debian and 7.6) - so the LSB should work.

Only error I see at backup is:

2014-10-01 13:55:09 Including build/default/99_update_os_conf.sh
/usr/src/rear/usr/share/rear/build/default/99_update_os_conf.sh: line 3: /tmp/rear.fD6uwSXFKiYEilv/rootfs//usr/src/rear/etc/rear/os.conf: No such file or directory
/usr/src/rear/usr/share/rear/build/default/99_update_os_conf.sh: line 6: /tmp/rear.fD6uwSXFKiYEilv/rootfs//usr/src/rear/etc/rear/os.conf: No such file or directory

@gdha gdha self-assigned this Oct 6, 2014

@gdha

This comment has been minimized.

Show comment
Hide comment
@gdha

gdha Oct 6, 2014

Member

@black187 sorry, on my fresh debian 7.6 system I could not reproduce your error...

Member

gdha commented Oct 6, 2014

@black187 sorry, on my fresh debian 7.6 system I could not reproduce your error...

@Reiner030

This comment has been minimized.

Show comment
Hide comment
@Reiner030

Reiner030 Oct 13, 2014

Contributor

There are 30+ packages which require lbs-release package - but it must not be installed automatically with basic server image.
But rear has the needed dependency to lsb-release (in github version minimal) as I see ;)

Contributor

Reiner030 commented Oct 13, 2014

There are 30+ packages which require lbs-release package - but it must not be installed automatically with basic server image.
But rear has the needed dependency to lsb-release (in github version minimal) as I see ;)

@gdha

This comment has been minimized.

Show comment
Hide comment
@gdha

gdha Oct 16, 2014

Member

@black187 for some reason the /etc/rear/os.conf was not generated during the backup. Perhaps you could run once read -vD mkrescue and send the log-file to us Also verify if your /tmp directory was writable for you?
I did the test myself today and it was created correctly. No idea why it did not work for you?

Member

gdha commented Oct 16, 2014

@black187 for some reason the /etc/rear/os.conf was not generated during the backup. Perhaps you could run once read -vD mkrescue and send the log-file to us Also verify if your /tmp directory was writable for you?
I did the test myself today and it was created correctly. No idea why it did not work for you?

@gdha

This comment has been minimized.

Show comment
Hide comment
@gdha

gdha Oct 17, 2014

Member

@Reiner030 in our rear.spec for RHEL/SLES we try to auto-create the /etc/rear/os.conf file so it is already present during the installation of the package. Perhaps, we could foresee something similar for Debian/Ubuntu as well? I am not an expert on debian package creation....

Member

gdha commented Oct 17, 2014

@Reiner030 in our rear.spec for RHEL/SLES we try to auto-create the /etc/rear/os.conf file so it is already present during the installation of the package. Perhaps, we could foresee something similar for Debian/Ubuntu as well? I am not an expert on debian package creation....

@gdha

This comment has been minimized.

Show comment
Hide comment
@gdha

gdha Nov 29, 2014

Member

@black187 this issue seems related to issue #512 !

Member

gdha commented Nov 29, 2014

@black187 this issue seems related to issue #512 !

@gdha

This comment has been minimized.

Show comment
Hide comment
@gdha

gdha Sep 7, 2016

Member

Added to the sponsor-list

Member

gdha commented Sep 7, 2016

Added to the sponsor-list

@gdha gdha closed this Sep 7, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment