Project

Profile

Help

Issue #4094

Architecture is not created if there are no architecture specific packages

Added by quba42 about 2 years ago. Updated 4 months ago.

Status:
NEW
Priority:
High
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version - Debian:
Platform Release:
Target Release - Debian:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Performance, Pulp 2
Sprint:
Quarter:

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:

  1. Parsing lists of all Packages to extract a list of one or two architectures is not good for performance.
  2. 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

Has duplicate Debian Support - Issue #5360: Debian Buster updates sync results in an empty Architectures field in the Release fileCLOSED - DUPLICATE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by mihai.ibanescu@gmail.com about 2 years 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 about 2 years 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 almost 2 years 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 almost 2 years ago

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.

#5 Updated by bmbouter over 1 year ago

  • Status changed from NEW to CLOSED - WONTFIX

#6 Updated by bmbouter over 1 year ago

  • Status changed from CLOSED - WONTFIX to NEW

Was closed as part of Pulp2 mass-fix, but reopening so the Debian plugin devs can determine what they want to do.

#7 Updated by bmbouter over 1 year ago

  • Tags Pulp 2 added

#8 Updated by mdellweg over 1 year ago

  • Severity changed from 2. Medium to 3. High
  • Triaged changed from No to Yes

#9 Updated by mdellweg over 1 year ago

  • Priority changed from Normal to High

#10 Updated by quba42 about 1 year ago

  • Has duplicate Issue #5360: Debian Buster updates sync results in an empty Architectures field in the Release file added

#11 Updated by quba42 about 1 year ago

As noted in https://pulp.plan.io/issues/5360, this also prevents the non created architectures from appearing in the relevant Release file.

#12 Updated by bmbouter 4 months ago

  • Tags Performance added
  • Tags deleted (Sync Performance)

Please register to edit this issue

Also available in: Atom PDF