Skip to content

ruby3.2-activesupport/7.2.2 package update - #32537

Closed
octo-sts[bot] wants to merge 3 commits into
mainfrom
wolfictl-1f8c8772-6b98-44bb-bc8c-fd86ad520577
Closed

ruby3.2-activesupport/7.2.2 package update#32537
octo-sts[bot] wants to merge 3 commits into
mainfrom
wolfictl-1f8c8772-6b98-44bb-bc8c-fd86ad520577

Conversation

@octo-sts

@octo-sts octo-sts Bot commented Oct 31, 2024

Copy link
Copy Markdown
Contributor

Signed-off-by: wolfi-bot <121097084+wolfi-bot@users.noreply.github.com>
@octo-sts octo-sts Bot added request-version-update request for a newer version of a package automated pr labels Oct 31, 2024
@octo-sts

octo-sts Bot commented Oct 31, 2024

Copy link
Copy Markdown
Contributor Author

Gen AI suggestions to solve the build error:

Based on the error logs, it appears the build is failing because of a missing dependency on the benchmark gem (version >= 0.3). The current version found is 0.2.1 which is insufficient. Here are the steps to fix this:

  1. Add ruby3.2-benchmark as a dependency in your package definition. Update your melange YAML file to include:
dependencies:
  runtime:
    - ruby3.2-benchmark # Add this line
    - ruby3.2-concurrent-ruby
    - ruby3.2-connection_pool 
    - ruby3.2-i18n
    - ruby3.2-securerandom
    - ruby3.2-tzinfo
  1. If ruby3.2-benchmark package doesn't exist in Wolfi repositories yet, you'll need to create it first. Create a new melange YAML file for ruby3.2-benchmark:
package:
  name: ruby3.2-benchmark
  version: 0.3.0
  epoch: 0
  description: "Benchmark module for Ruby"
  target-architecture:
    - all
  copyright:
    - paths:
      - "*"
      attestation: TODO
      license: Ruby

environment:
  contents:
    repositories:
      - https://packages.wolfi.dev/os
    packages:
      - busybox
      - ca-certificates-bundle
      - ruby-3.2

pipeline:
  - uses: ruby/gem
    with:
      gem: benchmark
      version: 0.3.0
  1. Build the benchmark package first, then rebuild your activesupport package.

The error indicates that ActiveSupport requires the benchmark gem version 0.3 or higher, but only version 0.2.1 is available in the system. Adding the proper benchmark dependency should resolve the issue.

@powersj

powersj commented Oct 31, 2024

Copy link
Copy Markdown
Member

This is saying it needs a newer version of benchmark. The benchmark gem is included in the main ruby distribution, so I believe we need to wait for a patch release of ruby with updated benchmark included.

3.2.5 is what we currently have.
3.2.6 was released Oct 30 (yesterday).
and merged 2 hours ago, will try rebase: #32582

@octo-sts

octo-sts Bot commented Oct 31, 2024

Copy link
Copy Markdown
Contributor Author

Gen AI suggestions to solve the build error:

Based on the error logs, it appears the build is failing because of a missing dependency on the benchmark gem version 0.3 or higher. The error specifically states:

Could not find 'benchmark' (>= 0.3) among 91 total gem(s) (Gem::MissingSpecError)

To fix this, you should:

  1. Add ruby3.2-benchmark as a dependency in your melange YAML file. Add it under the dependencies section:
dependencies:
  runtime:
    - ruby3.2-benchmark # Add this line
    - ruby3.2-concurrent-ruby
    - ruby3.2-connection_pool
    - ruby3.2-i18n
    - ruby3.2-securerandom
    - ruby3.2-tzinfo
  1. Make sure you have the correct version requirement. The error suggests you need benchmark >= 0.3, so you may need to update the benchmark package version in Wolfi if it's currently at 0.2.1.

  2. If the package doesn't exist yet in Wolfi, you may need to create a new package definition for ruby3.2-benchmark first.

These changes should resolve the dependency error and allow the build to complete successfully.

@octo-sts

octo-sts Bot commented Nov 4, 2024

Copy link
Copy Markdown
Contributor Author

Gen AI suggestions to solve the build error:

Based on the error logs, it appears the build is failing because of a missing dependency on the benchmark gem (version >= 0.3). The current system only has benchmark-0.2.1 installed, which doesn't meet the version requirement.

Here are the steps to fix this:

  1. Add benchmark as a dependency in your melange YAML file. Add it under the dependencies section:
dependencies:
  runtime:
    - ruby3.2-benchmark # Add this line
    - ruby3.2-concurrent-ruby
    - ruby3.2-connection_pool
    - ruby3.2-i18n
    - ruby3.2-securerandom
    - ruby3.2-tzinfo
  1. Make sure you have a package definition for ruby3.2-benchmark with version >= 0.3 in your Wolfi repository or create one if it doesn't exist.

  2. If you need to create the ruby3.2-benchmark package, create a new melange YAML file (ruby3.2-benchmark.yaml) with:

package:
  name: ruby3.2-benchmark
  version: 0.3.0
  epoch: 0
  description: "Benchmark module for Ruby"
  target-architecture:
    - all
  copyright:
    - paths:
      - "*"
      attestation: TODO
      license: Ruby

environment:
  contents:
    repositories:
      - https://packages.wolfi.dev/os
    packages:
      - busybox
      - ca-certificates-bundle
      - ruby-3.2

pipeline:
  - uses: ruby/gem
    with:
      gem: benchmark
      version: 0.3.0
  1. Build and test the benchmark package first, then rebuild your activesupport package.

This should resolve the dependency error and allow activesupport to build and test successfully.

@powersj

powersj commented Nov 4, 2024

Copy link
Copy Markdown
Member

It may be that we need to actually package up the benchmark gem and create a new package for it to get the latest version.

@octo-sts

octo-sts Bot commented Nov 7, 2024

Copy link
Copy Markdown
Contributor Author

superseded by #33613

@octo-sts octo-sts Bot closed this Nov 7, 2024
@octo-sts
octo-sts Bot deleted the wolfictl-1f8c8772-6b98-44bb-bc8c-fd86ad520577 branch November 8, 2024 00:02
justinvreeland pushed a commit to justinvreeland/wolfi that referenced this pull request May 6, 2026
Co-authored-by: staging-update-bot <staging-update-bot@chainguard.dev>

Export:  8a7ddcf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated pr request-version-update request for a newer version of a package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants