I’m seeing an issue with Debian connectors in ProGet 2026.03 when using Ubuntu 20.04 and 22.04 repositories.

The connector configuration itself is valid, for example:

and similarly:

ProGet reports that the local index was successfully updated, but the connector contains no packages. The generated local index remains essentially empty, around 32 KB.

For comparison, on the same ProGet instance:

Ubuntu 22.04:
jammy -> works
jammy-updates -> empty index with Components: all
jammy-security -> empty index with Components: all

Ubuntu 24.04:
noble -> works
noble-updates -> works
noble-security -> works

Ubuntu 26.04:
resolute -> works
resolute-updates -> works
resolute-security -> works

The issue also occurs with Ubuntu 20.04.

Network connectivity does not appear to be involved. From the ProGet host, the Ubuntu repository metadata can be downloaded successfully.

I also deleted the ProGet local connector index and allowed ProGet to rebuild it. ProGet again reported that the local index had been updated successfully, but the resulting index still contained no packages.

The local index sizes made the issue clear:

ubuntu-jammy -> 134 MB
ubuntu-jammy-updates -> 32 KB
ubuntu-jammy-security -> 32 KB

ubuntu-noble -> 152 MB
ubuntu-noble-security -> 34 MB
ubuntu-noble-updates -> 44 MB

I then changed the affected connectors from:

Components: all

to:

Components: main restricted universe multiverse

After doing this, ProGet indexed the packages correctly and the repositories started working normally.

So the issue seems to be specifically related to the special all value for Debian connector components. It works correctly for newer Ubuntu releases such as 24.04 and 26.04, but produces an empty local index for Ubuntu 20.04 and 22.04.

The particularly confusing part is that ProGet reports the local index as successfully updated even though no packages were indexed.

Thank you for your time and help.

Kind Regards.