Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ruby3.2-version_gem/1.1.4 package update #26560

Merged
merged 5 commits into from
Sep 8, 2024

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Aug 19, 2024

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 Aug 19, 2024
Copy link
Contributor Author

octo-sts bot commented Aug 19, 2024

Open AI suggestions to solve the build error:

The error message is: "ERROR:  While executing gem ... (Errno::ENOENT)
    No such file or directory @ rb_sysopen - /home/build/.ssh/gem-private_key.pem
    /usr/lib/ruby/3.2.0/rubygems/security/signer.rb:88:in `read'
    /usr/lib/ruby/3.2.0/rubygems/security/signer.rb:88:in `initialize'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:567:in `new'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:567:in `setup_signer'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:301:in `build'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:137:in `build'
    /usr/lib/ruby/3.2.0/rubygems/commands/build_command.rb:103:in `build_package'
    /usr/lib/ruby/3.2.0/rubygems/commands/build_command.rb:93:in `build_gem'
    /usr/lib/ruby/3.2.0/rubygems/commands/build_command.rb:73:in `execute'
    /usr/lib/ruby/3.2.0/rubygems/command.rb:328:in `invoke_with_build_args'
    /usr/lib/ruby/3.2.0/rubygems/command_manager.rb:253:in `invoke_command'
    /usr/lib/ruby/3.2.0/rubygems/command_manager.rb:193:in `process_args'
    /usr/lib/ruby/3.2.0/rubygems/command_manager.rb:151:in `run'
    /usr/lib/ruby/3.2.0/rubygems/gem_runner.rb:52:in `run'
    /usr/bin/gem:10:in `<main>'"

1. Verify the existence of `/home/build/.ssh/gem-private_key.pem`.
2. If missing, create or copy the `gem-private_key.pem` file to `/home/build/.ssh/`.
3. Ensure the file has the correct permissions: `chmod 600 /home/build/.ssh/gem-private_key.pem`.
4. Retry the gem command.

Copy link
Contributor Author

octo-sts bot commented Aug 19, 2024

Open AI suggestions to solve the build error:

The error message is: "ERROR:  While executing gem ... (Errno::ENOENT)
    No such file or directory @ rb_sysopen - /home/build/.ssh/gem-private_key.pem
    /usr/lib/ruby/3.2.0/rubygems/security/signer.rb:88:in `read'
    /usr/lib/ruby/3.2.0/rubygems/security/signer.rb:88:in `initialize'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:567:in `new'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:567:in `setup_signer'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:301:in `build'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:137:in `build'
    /usr/lib/ruby/3.2.0/rubygems/commands/build_command.rb:103:in `build_package'
    /usr/lib/ruby/3.2.0/rubygems/commands/build_command.rb:93:in `build_gem'
    /usr/lib/ruby/3.2.0/rubygems/commands/build_command.rb:73:in `execute'
    /usr/lib/ruby/3.2.0/rubygems/command.rb:328:in `invoke_with_build_args'
    /usr/lib/ruby/3.2.0/rubygems/command_manager.rb:253:in `invoke_command'
    /usr/lib/ruby/3.2.0/rubygems/command_manager.rb:193:in `process_args'
    /usr/lib/ruby/3.2.0/rubygems/command_manager.rb:151:in `run'
    /usr/lib/ruby/3.2.0/rubygems/gem_runner.rb:52:in `run'
    /usr/bin/gem:10:in `<main>'"

1. Verify the file path: Ensure `/home/build/.ssh/gem-private_key.pem` exists.
2. Check permissions: Ensure the file is readable by the user running the command.
3. If the file is missing, generate or obtain the required private key and place it in the specified directory.
4. Update the gem configuration to point to the correct key file if necessary.

Copy link
Contributor Author

octo-sts bot commented Aug 19, 2024

Open AI suggestions to solve the build error:

The error message is: "ERROR:  While executing gem ... (Errno::ENOENT)
    No such file or directory @ rb_sysopen - /home/build/.ssh/gem-private_key.pem
    /usr/lib/ruby/3.2.0/rubygems/security/signer.rb:88:in `read'
    /usr/lib/ruby/3.2.0/rubygems/security/signer.rb:88:in `initialize'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:567:in `new'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:567:in `setup_signer'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:301:in `build'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:137:in `build'
    /usr/lib/ruby/3.2.0/rubygems/commands/build_command.rb:103:in `build_package'
    /usr/lib/ruby/3.2.0/rubygems/commands/build_command.rb:93:in `build_gem'
    /usr/lib/ruby/3.2.0/rubygems/commands/build_command.rb:73:in `execute'
    /usr/lib/ruby/3.2.0/rubygems/command.rb:328:in `invoke_with_build_args'
    /usr/lib/ruby/3.2.0/rubygems/command_manager.rb:253:in `invoke_command'
    /usr/lib/ruby/3.2.0/rubygems/command_manager.rb:193:in `process_args'
    /usr/lib/ruby/3.2.0/rubygems/command_manager.rb:151:in `run'
    /usr/lib/ruby/3.2.0/rubygems/gem_runner.rb:52:in `run'
    /usr/bin/gem:10:in `<main>'"

1. Verify the file path: Ensure `/home/build/.ssh/gem-private_key.pem` exists.
2. Check permissions: Ensure the file is readable by the user running the command.
3. If the file is missing, generate or obtain the `gem-private_key.pem` and place it in the specified directory.
4. Update the path: If the key is located elsewhere, update the path in your gem configuration.

Copy link
Contributor Author

octo-sts bot commented Aug 25, 2024

Open AI suggestions to solve the build error:

The error message is: "ERROR:  While executing gem ... (Errno::ENOENT)
    No such file or directory @ rb_sysopen - /home/build/.ssh/gem-private_key.pem
    /usr/lib/ruby/3.2.0/rubygems/security/signer.rb:88:in `read'
    /usr/lib/ruby/3.2.0/rubygems/security/signer.rb:88:in `initialize'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:567:in `new'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:567:in `setup_signer'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:301:in `build'
    /usr/lib/ruby/3.2.0/rubygems/package.rb:137:in `build'
    /usr/lib/ruby/3.2.0/rubygems/commands/build_command.rb:103:in `build_package'
    /usr/lib/ruby/3.2.0/rubygems/commands/build_command.rb:93:in `build_gem'
    /usr/lib/ruby/3.2.0/rubygems/commands/build_command.rb:73:in `execute'
    /usr/lib/ruby/3.2.0/rubygems/command.rb:328:in `invoke_with_build_args'
    /usr/lib/ruby/3.2.0/rubygems/command_manager.rb:253:in `invoke_command'
    /usr/lib/ruby/3.2.0/rubygems/command_manager.rb:193:in `process_args'
    /usr/lib/ruby/3.2.0/rubygems/command_manager.rb:151:in `run'
    /usr/lib/ruby/3.2.0/rubygems/gem_runner.rb:52:in `run'
    /usr/bin/gem:10:in `<main>'"

1. Verify the file path: Ensure `/home/build/.ssh/gem-private_key.pem` exists.
2. Check permissions: Ensure the file is readable by the user running the command.
3. If the file is missing, generate or obtain the `gem-private_key.pem` and place it in the specified directory.
4. Update the gem configuration to point to the correct key file if the path is incorrect.

@developer-guy
Copy link
Member

for this one I created an issue here it looks like the maintainer started to sign the software with a private key defined in a variable named signing_key here so this is why the build breaks for now, so, I'm commenting the same into the issue.

Signed-off-by: Dentrax <furkan.turkal@chainguard.dev>
@Dentrax Dentrax force-pushed the wolfictl-4275bea4-8f89-4ca1-b572-90f45ca01a5d branch from 895bca7 to 6df9226 Compare September 8, 2024 06:45
Copy link
Contributor Author

octo-sts bot commented Sep 8, 2024

Open AI suggestions to solve the build error:

The error message is: "ERROR: failed to build package. the build environment has been preserved:
INFO   workspace dir: /temp/melange-workspace-1221626018
INFO   guest dir: /temp/melange-guest-3257035904
ERRO failed to build package: unable to run package ruby3.2-version_gem pipeline: unable to run pipeline: unable to run pipeline: exit status 1
make[1]: *** [Makefile:111: packages/aarch64/ruby3.2-version_gem-1.1.0-r1.apk] Error 1
make[1]: Leaving directory '/github/home'
make: *** [Makefile:101: package/ruby3.2-version_gem] Error 2
##[error]Process completed with exit code 2."

1. Verify dependencies for ruby3.2-version_gem.
2. Check the Makefile for correct paths and targets.
3. Ensure the build environment is correctly set up.
4. Run the build command manually to identify specific issues.
5. Review logs in /temp/melange-workspace-1221626018 for more details.

Copy link
Contributor

github-actions bot commented Sep 8, 2024

Package ruby3.2-version_gem: Click to expand/collapse

Package ruby3.2-version_gem:

.PKGINFO metadata:

  (
  	"""
  	# Generated by melange
  	pkgname = ruby3.2-version_gem
- 	pkgver = 1.1.0-r1
+ 	pkgver = 1.1.4-r0
  	arch = x86_64
- 	size = 115208
+ 	size = 120070
  	origin = ruby3.2-version_gem
  	pkgdesc = Versions are good. Versions are cool. Versions will win.
  	url = 
- 	commit = 6c3e34c97c3fc70a86207abd16afe6de997cd7c6
- 	builddate = 1721404986
+ 	commit = 98dcf4e039ca3b3a61329975fc956bd515192aac
  	license = MIT
  	depend = ruby-3.2
- 	datahash = ba3f2eb7b53c842de11f7eefd60d00039f803c2c6681e437754b462069ce29ae
+ 	datahash = 92e435c38e8e22e6281f7d105f34e0887aeecd3bda5a60fff289c48679fc20d4
  	"""
  )

Added: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.4/CHANGELOG.md
Added: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.4/CODE_OF_CONDUCT.md
Added: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.4/CONTRIBUTING.md
Added: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.4/LICENSE.txt
Added: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.4/README.md
Added: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.4/SECURITY.md
Added: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.4/lib/version_gem/api.rb
Added: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.4/lib/version_gem/basic.rb
Added: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.4/lib/version_gem/error.rb
Added: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.4/lib/version_gem/rspec.rb
Added: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.4/lib/version_gem/ruby.rb
Added: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.4/lib/version_gem/version.rb
Added: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.4/lib/version_gem.rb
Added: /usr/lib/ruby/gems/3.2.0/specifications/version_gem-1.1.4.gemspec
Deleted: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.0/CHANGELOG.md
Deleted: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.0/CODE_OF_CONDUCT.md
Deleted: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.0/CONTRIBUTING.md
Deleted: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.0/LICENSE.txt
Deleted: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.0/README.md
Deleted: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.0/SECURITY.md
Deleted: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.0/lib/version_gem/api.rb
Deleted: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.0/lib/version_gem/basic.rb
Deleted: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.0/lib/version_gem/error.rb
Deleted: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.0/lib/version_gem/rspec.rb
Deleted: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.0/lib/version_gem/version.rb
Deleted: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.0/lib/version_gem.rb
Deleted: /usr/lib/ruby/gems/3.2.0/gems/version_gem-1.1.0/sig/version_gem.rbs
Deleted: /usr/lib/ruby/gems/3.2.0/specifications/version_gem-1.1.0.gemspec

bincapz found differences: Click to expand/collapse

Moved: ruby3.2-version_gem/var/lib/db/sbom/ruby3.2-version_gem-1.1.0-r1.spdx.json -> /tmp/wolfictl-apk-3257169171/ruby3.2-version_gem/var/lib/db/sbom/ruby3.2-version_gem-1.1.4-r0.spdx.json (similarity: 0.98)

@developer-guy developer-guy merged commit d4b3de1 into main Sep 8, 2024
12 checks passed
@developer-guy developer-guy deleted the wolfictl-4275bea4-8f89-4ca1-b572-90f45ca01a5d branch September 8, 2024 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants