| View previous topic :: View next topic |
| Author |
Message |
Rockman8
n00b
Joined: 19 Sep 2023
Posts: 38
|
 Posted: Wed Oct 16, 2024 9:26 pm Post subject: libguestfs missing alias (symlink) for completed command |
 |
|
Hello,
I was trying to run vagrant package and I stumbled upon this
| Code: | vagrant package
==> default: Packaging domain...
==> default: Downloading learn_how_to_shell_script_through_project-based_training_default.img to /home/user/.vagrant.d/tmp/vagrant-package-20241016-29898-68f628/box.img
==> default: Image has backing image, copying image and rebasing ...
/home/user/.vagrant.d/gems/3.2.4/gems/vagrant-libvirt-0.12.2/lib/vagrant-libvirt/action/package_domain.rb:153:in ``': No such file or directory - virt-sysprep (Errno::ENOENT)
from /home/user/.vagrant.d/gems/3.2.4/gems/vagrant-libvirt-0.12.2/lib/vagrant-libvirt/action/package_domain.rb:153:in `sysprep_domain'
from /home/user/.vagrant.d/gems/3.2.4/gems/vagrant-libvirt-0.12.2/lib/vagrant-libvirt/action/package_domain.rb:73:in `package_v1'
from /home/user/.vagrant.d/gems/3.2.4/gems/vagrant-libvirt-0.12.2/lib/vagrant-libvirt/action/package_domain.rb:60:in `call'
from /home/user/.vagrant.d/gems/3.2.4/gems/vagrant-libvirt-0.12.2/lib/vagrant-libvirt/action/package_domain.rb:60:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/general/package.rb:87:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:117:in `block in finalize_action'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:117:in `block in finalize_action'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:117:in `block in finalize_action'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/builder.rb:183:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/runner.rb:104:in `block in run'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/util/busy.rb:22:in `busy'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/runner.rb:104:in `run'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/builtin/call.rb:56:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:117:in `block in finalize_action'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:117:in `block in finalize_action'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/builder.rb:183:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/runner.rb:104:in `block in run'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/util/busy.rb:22:in `busy'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/runner.rb:104:in `run'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/builtin/call.rb:56:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:117:in `block in finalize_action'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/builder.rb:183:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/runner.rb:104:in `block in run'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/util/busy.rb:22:in `busy'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/runner.rb:104:in `run'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/builtin/call.rb:56:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /home/user/.vagrant.d/gems/3.2.4/gems/vagrant-libvirt-0.12.2/lib/vagrant-libvirt/action/forward_ports.rb:202:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/builtin/config_validate.rb:28:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/general/package_setup_files.rb:49:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/general/package_setup_folders.rb:28:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:117:in `block in finalize_action'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/builder.rb:183:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/runner.rb:104:in `block in run'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/util/busy.rb:22:in `busy'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/runner.rb:104:in `run'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/builtin/call.rb:56:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/builtin/config_validate.rb:28:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/warden.rb:38:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/builder.rb:183:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/runner.rb:104:in `block in run'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/util/busy.rb:22:in `busy'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/action/runner.rb:104:in `run'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/machine.rb:247:in `action_raw'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/machine.rb:216:in `block in action'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/environment.rb:649:in `lock'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/machine.rb:202:in `call'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/machine.rb:202:in `action'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/plugins/commands/package/command.rb:97:in `package_vm'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/plugins/commands/package/command.rb:86:in `block in package_target'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/plugin/v2/command.rb:249:in `block in with_target_vms'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/plugin/v2/command.rb:238:in `each'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/plugin/v2/command.rb:238:in `with_target_vms'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/plugins/commands/package/command.rb:84:in `package_target'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/plugins/commands/package/command.rb:52:in `execute'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/cli.rb:67:in `execute'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/lib/vagrant/environment.rb:319:in `cli'
from /usr/lib64/ruby/gems/3.2.0/gems/vagrant-2.4.1/bin/vagrant:248:in `<main>'
|
Found out that I was missing app-emulation/libguestfs so I emerged it
| Code: | INFO: setup
Package: app-emulation/libguestfs-1.48.6-r1:0/1.48
Repository: gentoo
USE: abi_x86_64 amd64 elibc_glibc fuse gtk kernel_linux libvirt lua_single_target_lua5-1 ocaml perl python_single_target_python3_12
FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox
Determining the location of the kernel source code
Found kernel source directory:
/usr/src/linux
Found sources for kernel version:
6.6.52-gentoo-pietinger
Checking for suitable kernel configuration options ...
INFO: prepare
Running eautoreconf in '/var/tmp/portage/app-emulation/libguestfs-1.48.6-r1/work/libguestfs-1.48.6' ...
Running 'libtoolize --install --copy --force --automake' ...
Running 'aclocal -I m4 --system-acdir=/var/tmp/portage/app-emulation/libguestfs-1.48.6-r1/temp/aclocal' ...
Running 'autoconf --force' ...
Running 'autoheader --force' ...
Running 'automake --add-missing --copy --foreign --force-missing' ...
INFO: test
Skipping make test/check due to ebuild restriction.
INFO: install
Final size of build directory: 172908 KiB (168.8 MiB)
Final size of installed tree: 16892 KiB ( 16.4 MiB)
INFO: postinst
Please ensure you are in the 'kvm' group for decent performance!
Note that common tools like virt-resize are now part of app-emulation/guestfs-tools
QA: other
QA Notice: Problems with installed bash completions were found:
virt-diff: missing alias (symlink) for completed command.
virt-edit: missing alias (symlink) for completed command.
virt-alignment-scan: missing alias (symlink) for completed command.
virt-dib: missing alias (symlink) for completed command.
virt-filesystems: missing alias (symlink) for completed command.
virt-log: missing alias (symlink) for completed command.
virt-customize: missing alias (symlink) for completed command.
virt-inspector: missing alias (symlink) for completed command.
virt-get-kernel: missing alias (symlink) for completed command.
virt-sysprep: missing alias (symlink) for completed command.
virt-cat: missing alias (symlink) for completed command.
virt-ls: missing alias (symlink) for completed command.
virt-tail: missing alias (symlink) for completed command.
virt-builder: missing alias (symlink) for completed command.
virt-df: missing alias (symlink) for completed command.
virt-sparsify: missing alias (symlink) for completed command.
virt-resize: missing alias (symlink) for completed command.
virt-format: missing alias (symlink) for completed command.
virt-win-reg: missing alias (symlink) for completed command.
For more details on installing bash-completions, please see:
https://wiki.gentoo.org/wiki/Bash/Installing_completion_files
|
I got a bunch of missing alias including the virt-sysprep
So when I ran
it could not find virt-sysprep.
Also found this
https://bugs.gentoo.org/930590
and there's my build log too
https://pastebin.com/BQqxpkmm
Is there anyway around this? |
|
| Back to top |
|
 |
Rockman8
n00b
Joined: 19 Sep 2023
Posts: 38
|
| Posted: Thu Oct 17, 2024 6:23 pm Post subject: |
|
|
SOLVED
Turns out app-emulation/guestfs-tools was missing.
Perhaps adding a use flag to libguestfs would make clearer that there are tools that were moved to guestfs? Since guestfs and libguestfs share the same description, not indicating that guestfs has anything to do with libguestfs aside for its homepage description. |
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1990
|
| Posted: Thu Oct 17, 2024 6:48 pm Post subject: |
|
|
| Rockman8 wrote: | | Perhaps adding a use flag to libguestfs would make clearer that there are tools that were moved to guestfs? Since guestfs and libguestfs share the same description, not indicating that guestfs has anything to do with libguestfs aside for its homepage description. |
This is somewhat difficult as app-emulation/guestfs-tools needs app-emulation/libguestfs and adding a USE condition causes a circular dependency.
There is a message in the libguestfs ebuild: | Code: | | einfo "Note that common tools like virt-resize are now part of app-emulation/guestfs-tools" |
This really should be an elog or it gets buried in build output |
|
| Back to top |
|
|
Rockman8
n00b
Joined: 19 Sep 2023
Posts: 38
|
| Posted: Fri Oct 18, 2024 1:21 pm Post subject: |
|
|
| Code: | | "Note that common tools like virt-resize are now part of app-emulation/guestfs-tools" |
Yes I read that on the ebuild. If wasn't for that I would still guessing where did all the other tools had gone.
| Quote: | | This is somewhat difficult as app-emulation/guestfs-tools needs app-emulation/libguestfs and adding a USE condition causes a circular dependency. |
As USE condition you mean something mandatory or optional (would that make any difference or just the inclusion of the flag option itself would create a circular dependency)? Wouldn't be something like the order which package is installed (sorry for the noob question)?
And if it proves to be difficult then maybe a change on the description indicating the relationship between libguestsfs and guestfs wouldn't benefit those looking for it? |
|
| Back to top |
|
|
|
Other Things Gentoo
