Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • A apertis-issues
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

🔴 v2022.5 entered Hard Code Freeze, changes will not be accepted • schedule

🔴 v2023.1 entered Hard Code Freeze, changes will not be accepted • schedule

🟠 v2024dev2 entered Soft Code Freeze/Hard Feature Freeze, only bug fixes will be accepted • schedule

  • infrastructure
  • apertis-issues
  • Issues
  • #317
Closed
Open
Issue created May 02, 2023 by Walter Lozano@wlozanoMaintainer

Missing runtime dependency for rhosydd

Affected images versions

  • not relevant (explain why)
  • see the table below (list the *architecture and build id of the tested images in the appropriate cells)
Deployment Type v2021 v2022 v2023 v2024dev1
apt minimal/fixedfunction
ostree minimal/fixedfunction
apt target/hmi
ostree target/hmi
apt basesdk x x
apt sdk x x
apt nfs
apt lxc
apt image-builder
apt package-source-builder

To find the build id and the variant type you can:

  • derive it from the image name
    • for instance, with the apertis_ostree_v2022pre-fixedfunction-amd64-uefi_20211031.0425.img.gz image the build id is 20211031.0425, the variant is fixedfunction the deployment type is ostree
  • obtain it from /etc/os-release using the BUILD_ID and VARIANT_ID keys

Unaffected images versions

  • all versions up to XXX (replace XXX with the build id of the most recent Apertis images where this bug cannot be reproduced)
  • not relevant (explain why)
  • v2021 (explain why)
  • v2022 (explain why)

Testcase

The link to the testcase on https://qa.apertis.org/ if the bug was found during a testing round

Steps to reproduce

Build an image including rhosydd as in https://gitlab.apertis.org/infrastructure/apertis-image-recipes/-/jobs/2397966

Expected result

Image is built successfully

Actual result

Error arises

2023/04/27 13:48:30 apt | The following information may help to resolve the situation:

2023/04/27 13:48:30 apt | 

2023/04/27 13:48:30 apt | The following packages have unmet dependencies:

2023/04/27 13:48:30 apt |  rhosydd : Depends: policykit-1 (>= 0.113-1co2~) but 0.105-31+deb11u1+apertis2bv2023preb3 is to be installed

2023/04/27 13:48:30 apt | E: Unable to correct problems, you have held broken packages.

Reproducibility

How often the issue is hit when repeating the test and changing nothing (same device, same image, etc.)?

Put the ✅ in the most appropriate entry:

  1. ✅ always
  2. often, but not always
  3. rarely

Impact of bug

Package is not installable

Attachments

Add further information about the environment in the form of attachments here. Attach plain text files from log output (from journalctl, systemctl, …) or long backtraces as attached files. If adding comments on the log is required create a new snippet and add the link to it here.

Screenshots and videos are usually useful for graphic issues.

Root cause

The issue is caused by the fact that policykit-1 in v2022 and v2023 is older than the required version since it was synced from Debian Bullseye. However, in v2021 there was a newer version tracking upstream

https://gitlab.apertis.org/pkg/policykit-1/-/blob/apertis/v2021/debian/changelog

Outcomes

TBD

Management data

This section is for management only, it should be the last one in the description.

/cc @andrunko @em @sagar @sudarshan @wlozano Miss

Phabricator link: https://phabricator.apertis.org/T9692

Edited May 02, 2023 by Apertis CI robot
Assignee
Assign to
Time tracking
Apertis Website Terms of Use Privacy Policy