Project

Profile

Help

Issue #4094

closed

Architecture is not created if there are no architecture specific packages

Added by quba42 about 4 years ago. Updated over 1 year ago.

Status:
CLOSED - WONTFIX
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 - DUPLICATEActions
Actions #1

Updated by mihai.ibanescu@gmail.com about 4 years ago

That sounds reasonable.

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

Actions #2

Updated by quba42 about 4 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).

Actions #3

Updated by quba42 about 4 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.

Actions #4

Updated by quba42 about 4 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.

Actions #5

Updated by bmbouter over 3 years ago

  • Status changed from NEW to CLOSED - WONTFIX
Actions #6

Updated by bmbouter over 3 years 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.

Actions #7

Updated by bmbouter over 3 years ago

  • Tags Pulp 2 added
Actions #8

Updated by mdellweg over 3 years ago

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

Updated by mdellweg over 3 years ago

  • Priority changed from Normal to High
Actions #10

Updated by quba42 over 3 years ago

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

Updated by quba42 over 3 years ago

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

Actions #12

Updated by bmbouter over 2 years ago

  • Tags Performance added
  • Tags deleted (Sync Performance)
Actions #13

Updated by quba42 over 1 year ago

  • Status changed from NEW to CLOSED - WONTFIX

Pulp 2 issue WONTFIX.

Also available in: Atom PDF