kernel-firmware/kernel-firmware-brcm
SHA256
8
0
Fork 1
forked from pool/kernel-firmware-brcm
Code Pull Requests Activity

Do not conflict filesystem < 84 #1

Closed
dimstar wants to merge 1 commits from (deleted):main into main
pull from: (deleted):main
merge into: kernel-firmware:main
Conversation 3 Commits 1 Files Changed 2 +10 -1
dimstar commented 2025-04-25 14:28:13 +02:00
First-time contributor
Copy Link

Change conflicts filesystem < 84 to conflicts filesystem without
may-perform-usrmerge. Version 84 is specific to Tumbleweed; CODE 16
uses Version 16; yet we need to ensure we get an up-to-date
verion of filesystem. Relying on the recently introduced provides
instructing zypp about the usrmerge is perfect for this usecase.

Change conflicts filesystem < 84 to conflicts filesystem without may-perform-usrmerge. Version 84 is specific to Tumbleweed; CODE 16 uses Version 16; yet we need to ensure we get an up-to-date verion of filesystem. Relying on the recently introduced provides instructing zypp about the usrmerge is perfect for this usecase.
dimstar added 1 commit 2025-04-25 14:28:13 +02:00
Do not conflict filesystem < 84 07563206a4 
Change conflicts filesystem < 84 to conflicts filesystem without
may-perform-usrmerge. Version 84 is specific to Tumbleweed; CODE 16
uses Version 16; yet we need to ensure we get an up-to-date
verion of filesystem. Relying on the recently introduced provides
instructing zypp about the usrmerge is perfect for this usecase.
tiwai commented 2025-04-25 15:20:45 +02:00
Owner
Copy Link

Does this macro work also for SLE15-SP6 and SLE15-SP7, too?

In anyway, we need to fix the scripts in kernel-firmware-tools.git to generate the spec files, instead of patching each of them.

Does this macro work also for SLE15-SP6 and SLE15-SP7, too? In anyway, we need to fix the scripts in kernel-firmware-tools.git to generate the spec files, instead of patching each of them.
dimstar commented 2025-04-25 15:33:52 +02:00
Author
First-time contributor
Copy Link

Does this macro work also for SLE15-SP6 and SLE15-SP7, too?

Boolean dependencies were introduced in RPM 4.13 - the without enhancement added in RPM 4.14

https://rpm-software-management.github.io/rpm/manual/boolean_dependencies.html

> Does this macro work also for SLE15-SP6 and SLE15-SP7, too? Boolean dependencies were introduced in RPM 4.13 - the `without` enhancement added in RPM 4.14 https://rpm-software-management.github.io/rpm/manual/boolean_dependencies.html
tiwai commented 2025-04-25 15:45:31 +02:00
Owner
Copy Link

OK, thanks, then I'll fix as you suggested and apply to all kernel-firmware-* packages.

OK, thanks, then I'll fix as you suggested and apply to all kernel-firmware-* packages.
tiwai closed this pull request 2025-04-25 15:45:31 +02:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
RBrownFactory adamm autogits-devel dimstar_suse favogt_factory lkocman-factory maxlin_factory michals tiwai
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kernel-firmware/kernel-firmware-brcm#1
No description provided.
Delete Branch "(deleted):main"

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?