-
Notifications
You must be signed in to change notification settings - Fork 78
Open
Description
Some years ago we had the idea to have an IBS project containing multiple unreleased SLE changes. This is a decision made by the whole SUSE company, not just SUMA.
This project is now discontinued from our sumaform side, we still have content in those repos, but sumaform are not updating the injected reports according to the new SLE versions. So, in our test environments, we can't rely on that IBS project.
Example of code not update in the minima.yaml file:
# SLES 15 SP4 Test (not available until GM)
#- url: http://download.suse.de/ibs/SUSE:/Maintenance:/Test:/SLE-Module-Basesystem:/15-SP4:/x86_64/update
# archs: [x86_64]
#- url: http://download.suse.de/ibs/SUSE:/Maintenance:/Test:/SLE-Module-Containers:/15-SP4:/x86_64/update
# archs: [x86_64]
#- url: http://download.suse.de/ibs/SUSE:/Maintenance:/Test:/SLE-Module-Desktop-Applications:/15-SP4:/x86_64/update
# archs: [x86_64]
#- url: http://download.suse.de/ibs/SUSE:/Maintenance:/Test:/SLE-Module-Development-Tools:/15-SP4:/x86_64/update
# archs: [x86_64]
#- url: http://download.suse.de/ibs/SUSE:/Maintenance:/Test:/SLE-Module-Python2:/15-SP4:/x86_64/update
# archs: [x86_64]
#- url: http://download.suse.de/ibs/SUSE:/Maintenance:/Test:/SLE-Module-Server-Applications:/15-SP4:/x86_64/update
# archs: [x86_64]
#- url: http://download.suse.de/ibs/SUSE:/Maintenance:/Test:/SLE-Module-Web-Scripting:/15-SP4:/x86_64/update
# archs: [x86_64]
-
Should we make a cleanup and remove these repos completely from sumaform and so the parameter too?
-
Should we work in an update of this part?
-
Should we rethink it and do it differently?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels