pool/agama-products
SHA256
17
0
Fork 2
Code Issues Pull Requests Activity

Change the openSUSE autoinstallation IDs (bsc#1249399) #1

Merged
smithfarm merged 1 commits from lslezak/agama-products:leap-16.0 into leap-16.0 2025-09-16 11:40:56 +02:00
Conversation 2 Commits 1 Files Changed 5 +32 -7
lslezak commented 2025-09-12 17:30:52 +02:00
Contributor
Copy Link

Problem

Solution

Change the openSUSE Leap autoinstallation ID from "Leap_16.0" to "openSUSE_Leap" and the openSUSE Leap Micro ID from "LeapMicro_6.2" to "openSUSE_Leap_Micro".

This allows using the same autoinstallation profile in future versions as the version is not hardcoded in the profile.

## Problem - https://bugzilla.suse.com/show_bug.cgi?id=1249399 - Using a version number for the product specifier in the autoinstallation profile will not allow using the same profile in the future Leap 16.1 without changes. ## Solution Change the openSUSE Leap autoinstallation ID from "Leap_16.0" to "openSUSE_Leap" and the openSUSE Leap Micro ID from "LeapMicro_6.2" to "openSUSE_Leap_Micro". This allows using the same autoinstallation profile in future versions as the version is not hardcoded in the profile.
lslezak added 1 commit 2025-09-12 17:30:52 +02:00
Change the openSUSE autoinstallation IDs (bsc#1249399) 1c2d18ceb1 
Change the openSUSE Leap autoinstallation ID from "Leap_16.0"
to "openSUSE_Leap" and the openSUSE Leap Micro ID from
"LeapMicro_6.2" to "openSUSE_Leap_Micro".

This allows using the same autoinstallation profile in future versions.
smithfarm commented 2025-09-16 11:40:37 +02:00
Owner
Copy Link

Ideally, the change would land in factory branch, first, and then the leap-16.0 branch would be updated to the exact same git hash that is in factory...

But the factory branch is behind, so we are building up a parallel history in each branch, even though the code is presumably exactly the same.

Ideally, the change would land in `factory` branch, first, and then the `leap-16.0` branch would be updated to the exact same git hash that is in `factory`... But the factory branch is behind, so we are building up a parallel history in each branch, even though the code is presumably exactly the same.
smithfarm approved these changes 2025-09-16 11:40:51 +02:00
smithfarm merged commit ba418bd1e6 into leap-16.0 2025-09-16 11:40:56 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
smithfarm
Labels
Clear labels
legaldb
Critical Priority
Critical legaldb priority
Archived
legaldb
High Priority
2
High legaldb priority
legaldb
Normal Priority
1
Normal legaldb priority
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
adamm_super adrianSuSE autobuild-owner autobuild-review autogits_workflow_pr_bot bigironman dirkmueller eroca factory_bot gitea_test legaldb lkocman-factory maxlin_factory opensuse-review packagehub-review smithfarm
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: pool/agama-products#1
Delete Branch "lslezak/agama-products:leap-16.0"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?