asbru-cm / asbru-cm

Ásbrú Connection Manager is a user interface that helps organizing remote terminal sessions and automating repetitive tasks.

Home Page:https://www.asbru-cm.net/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Could not resolve all dependencies on current Arch

bryanpedini opened this issue · comments

Describe the bug
Installing on Arch gives "Could not resolve all dependencies" error.

To Reproduce
Steps to reproduce the behavior:

  1. git clone https://aur.archlinux.org/asbru-cm-git.git
  2. cd asbru-cm-git
  3. makepkg -cris

Expected behavior
Installation of the program

Screenshots
Screenshot_20220103_100359

Environment (please complete the following information):

  • OS: Arch
  • Ásbrú Version: master of AUR

Additional context

Full (text) log of what happens:
==> Making package: asbru-cm-git 6.3.2.r5.gdacd5d9-1 (Mon 03 Jan 2022 09:52:40 AM CET)
==> Checking runtime dependencies...
==> Installing missing dependencies...
[sudo] password for bryanpedini: 
error: target not found: perl-expect
error: target not found: perl-crypt-cbc<3
error: target not found: perl-net-arp
error: target not found: uuid
error: target not found: perl-crypt-rijndael
error: target not found: perl-io-stty
==> ERROR: 'pacman' failed to install missing dependencies.
==> Missing dependencies:
-> vte3
-> cairo-perl
-> glib-perl
-> pango-perl
-> perl-socket6
-> perl-expect
-> perl-yaml
-> perl-crypt-cbc<3
-> perl-crypt-blowfish
-> perl-gtk3
-> perl-net-arp
-> uuid
-> perl-crypt-rijndael
-> perl-gtk3-simplelist
-> perl-io-stty
-> perl-io-tty
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.

Migration from PAC currently in progress once I get this to work.
Thank you in advance for this fork!

You'd better ask to the packager directly (see https://aur.archlinux.org/packages/asbru-cm-git) and in particular, I think this should answer your question --> https://aur.archlinux.org/packages/asbru-cm-git#comment-760778

Thank you for your suggestion @gfrenoy, however neither makepkg -cris nor yay -S solved this issue for me.
I'll try to contact the packager via AUR and in the meanwhile I'll use a Docker container with X11 forwarded (just like I do with PAC right now).