[opensuse] Trying to understand the opensuse release cycle of updates, packages, patches, security updates
Kind LPs, was always trying to understand the opensuse release mechanisms and cycles of packages, updates, patches, security fixes etc. To bridle the horse from behind, updates/fixes arrive e.g. at: <http://download.opensuse.org/update/leap/15.0/oss/rpms/x86_64/?C=M;O=D> Before that, I kinda figured, there would be the place at: <http://download.opensuse.org/update/leap/15.0-test/> How does stuff from -test move over to the final area? Are the files the very same and are only moved over, so binary identical, signatures and hash files identical? I recall this recent incident when the whole final update directory was hosed and needed to be rebuilt from scratch just like a week ago and files were regenerated all over. So before test, or related to test, there is the build system with all kinds of weird things and abbreviations :), swamp integration, obs build request tickets <https://build.opensuse.org/request/show/690934> inside bugzilla tickets there be whiteboard entry lines
obs:running:123456:important
and what not Often I see respins of packages (e.g. kernel here) with the hints of adding or removing stuff over again due to regressions etc. intel i915 module and so on just as an example. Anyone care to explain a bit more details of these things, especially the last steps, from aboce, when and how does a package file land in test, do all of the releases land in there, who or what tests them, voluntarily community testing, or some automated testing of those files as well, and how and when do they move over to the final area and be released, or do they be built over again from scratch to make em land in final place and so forth. Is the testing directory area be discussed somewhere? Is there a list or a place or a group or forum, who and where they test this place and then they push or flag them after successfull testing for a general release? TIA. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Apr 08, 2019 at 12:22:58PM +0200, cagsm wrote:
Kind LPs,
was always trying to understand the opensuse release mechanisms and cycles of packages, updates, patches, security fixes etc.
To bridle the horse from behind, updates/fixes arrive e.g. at: <http://download.opensuse.org/update/leap/15.0/oss/rpms/x86_64/?C=M;O=D>
Before that, I kinda figured, there would be the place at: <http://download.opensuse.org/update/leap/15.0-test/>
How does stuff from -test move over to the final area? Are the files the very same and are only moved over, so binary identical, signatures and hash files identical? I recall this recent incident when the whole final update directory was hosed and needed to be rebuilt from scratch just like a week ago and files were regenerated all over.
This was hopefully a one time incident.
So before test, or related to test, there is the build system with all kinds of weird things and abbreviations :), swamp integration, obs build request tickets
<https://build.opensuse.org/request/show/690934>
inside bugzilla tickets there be whiteboard entry lines
obs:running:123456:important
and what not
Often I see respins of packages (e.g. kernel here) with the hints of adding or removing stuff over again due to regressions etc. intel i915 module and so on just as an example.
Anyone care to explain a bit more details of these things, especially the last steps, from aboce, when and how does a package file land in test, do all of the releases land in there, who or what tests them, voluntarily community testing, or some automated testing of those files as well, and how and when do they move over to the final area and be released, or do they be built over again from scratch to make em land in final place and so forth.
Is the testing directory area be discussed somewhere? Is there a list or a place or a group or forum, who and where they test this place and then they push or flag them after successfull testing for a general release?
There is a video where we (or I) explain the maintenance process a bit. https://www.youtube.com/watch?v=R9OMOWIDICw from 2 years ago. The -test repo has RPMs similar to the released ones, but they get resigned during release. So they have the same bianries, but not the same signature. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Apr 8, 2019 at 1:14 PM Marcus Meissner <meissner@suse.de> wrote:
There is a video where we (or I) explain the maintenance process a bit. https://www.youtube.com/watch?v=R9OMOWIDICw from 2 years ago.
thank you for the video. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
cagsm -
Marcus Meissner