Problem with update submissions to Leap 15.4 and Leap 15.5
Hi, Could someone please tell us who is responsible for the final push of updates to the Leap 15.4 and Leap 15.5 repositories? My collaborator (the other Larry) and I work very hard testing the latest release of VirtualBox and fixing any bugs that we discover. In all cases, we have received a positive review, but, our bug fixes either take a very long time to propagate through the system, or they never make it before we have another fix. This is exceedingly frustrating as we know from Tumbleweed that such fixes can propagate through OBS in only a few days! Thanks Dominique/Dimstar. Each of these fixes has a Bugzilla entry that is referenced in the Changes file, and in the submission entry. Surprisingly, the latest fix for Leap 15.3, which is out of maintenance, made it through, even though 15.4 and 15.5 have not yet! Thanks for any info. Larry
Hi, On Thu, Jan 12, 2023 at 01:34:31PM -0600, Larry Finger wrote:
Hi,
Could someone please tell us who is responsible for the final push of updates to the Leap 15.4 and Leap 15.5 repositories?
My collaborator (the other Larry) and I work very hard testing the latest release of VirtualBox and fixing any bugs that we discover. In all cases, we have received a positive review, but, our bug fixes either take a very long time to propagate through the system, or they never make it before we have another fix. This is exceedingly frustrating as we know from Tumbleweed that such fixes can propagate through OBS in only a few days! Thanks Dominique/Dimstar.
Each of these fixes has a Bugzilla entry that is referenced in the Changes file, and in the submission entry.
Surprisingly, the latest fix for Leap 15.3, which is out of maintenance, made it through, even though 15.4 and 15.5 have not yet!
Thanks for any info.
Hi, that would be me (as you know), or also Robert Frohl who is backing me up currently. I am still on leave this week, so not that attentive to openSUSE maintenance. Challenges for us are: - openqa redness on for openSUSE Leap, so automation does not work. - We cannot release virtualbox for the same kernel update twice (e.g. more than once a month), as the kmps will cause a zypper error whcih openqa is not handling. - Absences Ciao, Marcus
On Thu, Jan 12, 2023 at 09:51:52PM +0100, Marcus Meissner wrote:
Hi,
On Thu, Jan 12, 2023 at 01:34:31PM -0600, Larry Finger wrote:
Hi,
Could someone please tell us who is responsible for the final push of updates to the Leap 15.4 and Leap 15.5 repositories?
My collaborator (the other Larry) and I work very hard testing the latest release of VirtualBox and fixing any bugs that we discover. In all cases, we have received a positive review, but, our bug fixes either take a very long time to propagate through the system, or they never make it before we have another fix. This is exceedingly frustrating as we know from Tumbleweed that such fixes can propagate through OBS in only a few days! Thanks Dominique/Dimstar.
Each of these fixes has a Bugzilla entry that is referenced in the Changes file, and in the submission entry.
Surprisingly, the latest fix for Leap 15.3, which is out of maintenance, made it through, even though 15.4 and 15.5 have not yet!
Thanks for any info.
Hi, that would be me (as you know), or also Robert Frohl who is backing me up currently. I am still on leave this week, so not that attentive to openSUSE maintenance.
Challenges for us are:
- openqa redness on for openSUSE Leap, so automation does not work. - We cannot release virtualbox for the same kernel update twice (e.g. more than once a month), as the kmps will cause a zypper error whcih openqa is not handling. - Absences
Hmm, 15.5 responsible is the Leap GA team, Max Lin or Lubos Kocman. Ciao, marcus
On 1/12/23 14:51, Marcus Meissner wrote:
Hi, that would be me (as you know), or also Robert Frohl who is backing me up currently. I am still on leave this week, so not that attentive to openSUSE maintenance.
Challenges for us are:
- openqa redness on for openSUSE Leap, so automation does not work. - We cannot release virtualbox for the same kernel update twice (e.g. more than once a month), as the kmps will cause a zypper error whcih openqa is not handling. - Absences
Marcus, Thanks for the prompt action on the VB update for 15.4 - it was available late today. I understand that holidays and vacations would affect the throughput, but I'm afraid that the first two reasons are opaque to me. Also thank you for the tip on the contact for 15.5. Larry
participants (2)
-
Larry Finger -
Marcus Meissner