Issue #4094: Architecture is not created if there are no architecture specific packages - Debian Support - Pulp

Send by e-mail

Issue #4094

Architecture is not created if there are no architecture specific packages

Added by quba42 over 1 year ago. Updated 16 days ago.

Status:

NEW

Priority:

High

Assignee:

Start date:

Due date:

Estimated time:

Severity:

3. High

Version - Debian:

Platform Release:

Target Release - Debian:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Performance, Pulp 2

Sprint:

Description

Current Behavior: Since the architectures supported by a repository are parsed from the packages list in the mongodb, architectures included in an upstream repository are not created if there are no architecture specific packages.

Expected Behavior: The architectures should be created containing only "architectures = all" type packages.

Proposed Approach:

There should be a units_deb_arches collection in the mongodb in addition to the existing units_deb_component, units_deb_release, and units_deb collections.

This would have at least two additional benefits beyond fixing this bug:

Parsing lists of all Packages to extract a list of one or two architectures is not good for performance.
It is conceptually correct. Debian repositories are built from a pool of all packages, along with meta data that will allow you to identify useful subsets of these packages using a combination of releases, components, and architectures. The database should mirror this conceptual division.

Related issues

History

#1 Updated by mihai.ibanescu@gmail.com over 1 year ago

That sounds reasonable.

I don't think I understand the use of architectures = all, so I'll need to do some research.

#2 Updated by quba42 over 1 year ago

I am currently working on refactoring the relevant code for better performance.
Once that is done I may look into fixing this bug as well (if I can find the time).

#3 Updated by quba42 over 1 year ago

The following pull request (https://github.com/pulp/pulp_deb/pull/57) now mentions this Bug. While this pull request does not fix the bug it lays the groundwork for doing so as mentioned above.

#4 Updated by quba42 over 1 year ago

mihai.ibanescu@gmail.com wrote:

I don't think I understand the use of architectures = all, so I'll need to do some research.

My understanding is that these are packages that are architecture independent packages (for example packages containing documentation) that can therefore be included with any architecture.