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
  • #321
Closed
Open
Issue created May 15, 2023 by Benani Sagar Kishore@sagarDeveloper

devroot testcase fails on v2023.1 SDK

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 20230503.0116
apt sdk 20230503.0116
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

  • v2023.0

Testcase

https://qa.apertis.org/testcases/v2023dev2/devroot-manual-arm64.html

Steps to reproduce

https://qa.apertis.org/testcases/v2023dev2/devroot-manual-arm64.html After executing step 7 observe the logs

Expected result

no errors should be seen

Actual result

user@apertis:~$ sudo  apt-get source dlt-daemon
Reading package lists... Done
Need to get 5102 kB of source archives.
Get:1 https://repositories.apertis.org/apertis v2023/target dlt-daemon 2.18.6-1+deb11u1+apertis1 (diff) [7960 B]
Get:2 https://repositories.apertis.org/apertis v2023/target dlt-daemon 2.18.6-1+deb11u1+apertis1 (dsc) [1320 B]
Get:3 https://repositories.apertis.org/apertis v2023/target dlt-daemon 2.18.6-1+deb11u1+apertis1 (tar) [5092 kB]
Fetched 5102 kB in 20s (252 kB/s)                                                                                                                                                            
dpkg-source: info: extracting dlt-daemon in dlt-daemon-2.18.6
dpkg-source: info: unpacking dlt-daemon_2.18.6.orig.tar.gz
dpkg-source: info: unpacking dlt-daemon_2.18.6-1+deb11u1+apertis1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 0001-Fix-a-double-free-bug.patch
W: Download is performed unsandboxed as root as file 'dlt-daemon_2.18.6-1+deb11u1+apertis1.debian.tar.xz' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
user@apertis:~$ sudo apt-get build-dep dlt-daemon
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libsystemd-dev : Depends: libsystemd0 (= 247.3-7+apertis1bv2023dev3b3) but 247.3-7+apertis1bv2023.0bb1 is to be installed
E: Unable to correct problems, you have held broken packages.
user@apertis:~$ 
user@apertis:~$ 

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

Impact of bug

High

Root cause

tbd

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

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

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