Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

aptitude-run-state-bundle

aptitude-run-state-bundle -V (return code: 1)


bzip2: Compressed file ends unexpectedly;
 perhaps it is corrupted?  *Possible* reason follows.
bzip2: Inappropriate ioctl for device
 Input file = (stdin), output file = (stdout)

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Removing /tmp/aptitudebug.GLcvmpGyp
aptitude-run-state-bundle --help (return code: 1)

Usage: /usr/bin/aptitude-run-state-bundle [options] <input-file> [<program> [arguments ...]]

This command will unpack the given archive of aptitude state
information, then invoke the given program with the given
list of arguments, passing appropriate -o options to cause
aptitude to use the contents of that archive as its global
data store.

Options:
  --append-args    Place the generated arguments at the end of
                   the command line (default).
  --help           Display this message and exit.
  --no-clean       Do not remove the temporary directory after
                   invoking aptitude.
  --prepend-args   Place the generated arguments at the beginning
                   of the command line.
  --really-clean   Remove the state directory, even if --statedir
                   was passed as an argument.
  --statedir       The <input-file> is an unpacked aptitude bundle,
                   not a bundle file; implicitly sets --no-clean.
  --unpack         Just unpack the <input-file>, don't run aptitude.

Comments

Popular posts from this blog

PostgreSQL Pgbadger Installation On Linux

PostgreSQL pgBadger

How to configure Replication Manager (repmgr) ?

7 Steps to configure BDR replication in postgresql

Postgresql Database Tutorial android app