Bug 1217642 - Hawk Gemfile.lock should be generaged on the client side
Summary: Hawk Gemfile.lock should be generaged on the client side
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: High Availability (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: SUSE Linux Enterprise High Availability Team
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-29 10:12 UTC by Aleksei Burlakov
Modified: 2023-11-29 10:12 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Aleksei Burlakov 2023-11-29 10:12:48 UTC 
The build system creates the Gemfile.lock according to its configuration and packs and provides it together with hawk. If the client has other gem files than the build system, the client's hawk might be misconfigured. The hawk package needs to provide the blank Gemfile.lock to let the client machine generate it itself (with respect to its gem files).