oxidecomputer / oxidecomputer/helios-engvm

Failure mode in pkg update: cpqary3, smrt

Open
#34 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
64
Forks
9
PR merge metrics
No merged PRs in 30d

Description

I ran into a couple issues with the cpqary3 and smrt drivers when running pkg update on a new install of helios-engvm.

pkg://helios-dev/driver/storage/cpqary3@0.5.11,5.11-2.0.23833:20260318T211716Z delivers multiple copies of driver cpqary3
This package must be corrected before it can be installed.

pkg://helios-dev/driver/storage/smrt@0.5.11,5.11-2.0.23833:20260318T211717Z delivers multiple copies of driver smrt
This package must be corrected before it can be installed.

The problem mirrors: https://illumos.topicbox.com/groups/omnios-discuss/Te1ef9c3f5aea0dd0

with possible solution akin to OmniOS scheme of stepping through upgrades: https://omnios.org/upgrade

or a more permanent version of pkg uninstall entire.

https://github.com/oxidecomputer/falcon-image-netstack/pull/2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing pkg update on a new helios-engvm install and inspect how the cpqary3 and smrt packages deliver duplicate drivers. Compare the proposed OmniOS upgrade-stepping approach and the linked falcon-image-netstack pull request; done means the affected packages can be upgraded without the multiple-copy failure.

Written by the indexing model from the issue text.

Assessment

Domain
operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.