Apt repo architecture conflict

Hello everyone i’m new here,
i’m working on a project that uses RPI’s for user interaction, i used to inject my deb packets manually inside these pi’s, but now i’m automatic everything and using a nexus3 as its repository :slight_smile:

I do have a question regarding working with apt repo’s
i’m having problems downloading my packets from our apt nexus,
when doing inserting the url of the repo and doing a apt update, its telling me there is no support for armhf (or even arm64, i386…)
These packets ofcourse work on my pi’s as i use them now.

blurred confidential information

this also happens when trying to download from my ubuntu system (i386).
now when i go browse inside the repo and look at its attributes, it saying architecture all as it should be i guess?

image may be broken in the future

And when looking inside the html index its also saying all

image may be broken in the future

i really no idea what is causing this problem and how i can solve/ work around this, since apt is also not giving an option to ‘ignore’ architectures, because i’m assuming its not even finding any.
Tried adding arm64 & i386 with dpkg --add-architecture, but with no avail.

Thanks in advance, kind regards Gene

1 Like

Hi Gene! Let me check. I will try to help you.

1 Like

@gene just FYI still in progress. I hope today/tomorrow will have some information. I didn’t had a lot of time. Sorry for delay.

Hi @gene!
Two small questions.

  1. Are you running all this on the real Raspberry PI? or some virtual machine?
  2. As far as I understand you also have an error messages if perform ‘apt update’ without using Nexus? correct me if i wrong.


Hello @aornatovskyy

Yes iam running this on Real Raspbian pie’s 3 & 4.

Well, i add the nexus apt repo to the pi, therefore its giving the architecture all error.
there are ofcourse no problems when this nexus apt repo is not added.
Hope this answered your questions!

Greets & thanks, Gene

@gene Interesting issue. I will try to play around. Will update you as soon I have some results.

1 Like

@gene hi! I can’t reproduce your issue. May be i missed something.

Here is my topology.

RASBIAN-REPO (http://raspbian.raspberrypi.org/raspbian)
RASBERRY Pi client 3 (ip:

I have one question for you. You didn’t provide the url to the Remote repository. Is it also http://raspbian.raspberrypi.org/raspbian or it is different?

Hello. I think it is related to 'all' arch apparently not honored by repo · Issue #105 · sonatype-nexus-community/nexus-repository-apt · GitHub

My humble investigation shows that:

Packages under ‘all’ architecture are not part of Packages file for amd64 or any specific arch.
apt-get should scan Packages file for ‘all’ architecture if ‘all’ is present in Architecures list in Release file.

But it does not work in apt version 1.0.9 (debian jessie). It is working on 1.4 (debian stretch).


1 Like

Hello, I’m getting warning message of command “apt update”
N: Skipping acquire of configured file ‘main/binary-amd64/Packages’ as repository ‘http:///repository/apt-bionic-ansible bionic InRelease’ doesn’t support architecture ‘amd64’
N: Skipping acquire of configured file ‘main/binary-amd64/Packages’ as repository 'http://
/repository/apt-hosted bionic InRelease’ doesn’t support architecture ‘amd64’

I can see that some of APT hosted repository have binary-all and binary-amd64 metadata files and some of then only binary-all.

  1. When file “binary-amd64” is created?
  2. Can you hide this warning massages that repository doesn’t support architecture ‘amd64’?