Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add aarch64 compatibility for all dependencies #3338

Closed
moham96 opened this issue Feb 25, 2022 · 12 comments
Closed

add aarch64 compatibility for all dependencies #3338

moham96 opened this issue Feb 25, 2022 · 12 comments
Labels
type::bug Valid bug

Comments

@moham96
Copy link

moham96 commented Feb 25, 2022

Bug description

Can't install blackarch on top of an aarch64 archlinuxarm base (virtual machine)

Steps to reproduce

  • fire up a generic aarch64 archlinuxarm vm (for me i used UTM on macos as a qemu gui)
  • update the system and follow these steps to install blackarch
  • you will see that in the last step (issuing pacman -S blackarch) that there are many unresolvable dependencies (see below debug log for full pacman output)
  • using the command with the --overwrite argument doesn't resolve the issue either
    Actual result: Describe here what happens after you run the steps above (i.e. the buggy behaviour)
    The packages don't install due to unresolvable dependencies

Expected result: Describe here what should happen after you run the steps above (i.e. what would be the correct behaviour)

The packages should install fine

Screenshots

Info for developers

Device: Apple macbook air m1 2020
GNU/Linux distribution: Host is MacOS 12.2.1 Guest is archlinuxarm inside a UTM virtual machine
Tool version: N/A

Link to debug log

https://www.toptal.com/developers/hastebin/ahuhabuyej.yaml

@moham96 moham96 added the type::bug Valid bug label Feb 25, 2022
@noraj
Copy link
Contributor

noraj commented Feb 25, 2022

I'm not sure but this section states that it requires a platform listed here and MAC M1 are not.

@moham96
Copy link
Author

moham96 commented Feb 25, 2022

@noraj i'm not running it on native m1, it's running as a generic aarch64 VM so it is supported, my guess is there is a problem with the packaging not with anything related to the platform

@moham96
Copy link
Author

moham96 commented Feb 27, 2022

Just to be sure I downloaded ArchLinuxARM-aarch64-latest.tar.gz and run it in a chroot inside a Ryzen 5 x86 machine(to find if the m1 is the culprit) and the same problem exists

@ikstream
Copy link
Member

Thank you for reporting, we identified the problem, but it will take a moment to address it.

@moham96
Copy link
Author

moham96 commented Mar 1, 2022

@ikstream can we have more info about the issue ? is it on blackarch side? on archlinuxarm side? any ETA?

Regards

@ikstream
Copy link
Member

ikstream commented Mar 3, 2022

It's a problem on our side. While the packages have arch=any they are not in the alarm repos. So we need to package and test them for aarch64.
We are currently looking to release a new x86 iso and the aarch64 user share seems to be relatively small so far.
Nevertheless we will take care of the issue as soon as possible, but the priority is on x86.

It should be possible to install individual tools however.

@noraj
Copy link
Contributor

noraj commented Mar 3, 2022

Never do pacman -S blackarch it is useless and will never work anyway on any platform as there will always be at least one tool failing among 2800+ tools.

@noraj noraj closed this as completed Mar 3, 2022
@ikstream
Copy link
Member

ikstream commented Mar 4, 2022

As this is still an issue we need to address and not all dependencies are available on aarch64, I would keep this issue open until it's fixed.

@ikstream ikstream reopened this Mar 4, 2022
@noraj noraj changed the title warning: cannot resolve "X", a dependency of "Y" add aarch64 compatibility for all dependencies Mar 4, 2022
@moham96
Copy link
Author

moham96 commented Mar 4, 2022

Never do pacman -S blackarch it is useless and will never work anyway on any platform as there will always be at least one tool failing among 2800+ tools.

pacman -S blackarch is mentioned in the docs, if it doesn't work it shouldn't be there.
There should not be a tool failing to install since we are not building from source so every tool should ideally be possible to install with no problem.

Regards

@ikstream
Copy link
Member

ikstream commented Mar 4, 2022

You are not building from source, but we do for packaging (for some).

There is a discussion to remove the mentioned line from docs.

@BlackArch BlackArch locked and limited conversation to collaborators Mar 4, 2022
@noraj
Copy link
Contributor

noraj commented Jul 14, 2022

pacman -S blackarch has been removed from the doc BlackArch/blackarch-site#152

@noptrix
Copy link
Contributor

noptrix commented Dec 15, 2024

These issues should be resolved. However, there may be some unresolved ones that are flagged as warnings. You can exclude these packages and its dependencies by confirming 'yes' when prompted to skip the installation of unresolved packages.

@noptrix noptrix closed this as completed Dec 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type::bug Valid bug
Projects
None yet
Development

No branches or pull requests

4 participants