Hi,
I would like to submit a MR for a Leap 15 package which is shared with SLE-15.
I have read https://en.opensuse.org/openSUSE:Maintenance_update_process
but obviously, the flowgraph is a dead end after the first decision ...
So, what do to in this case? File a bug report and wait for someone to pick it up?
Kind regards, Stefan
-- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019
On Tue, Jul 03, 2018 at 03:29:20PM +0000, Brüns, Stefan wrote:
Hi,
I would like to submit a MR for a Leap 15 package which is shared with SLE-15.
I have read https://en.opensuse.org/openSUSE:Maintenance_update_process
but obviously, the flowgraph is a dead end after the first decision ...
So, what do to in this case? File a bug report and wait for someone to pick it up?
Yes, file a bugreport... If you there is a SUSE Maintainer on it, you can also drop him/her an email with your patch or so.
Ciao, Marcus
On Wed, 04 Jul 2018 07:47:29 +0200, Marcus Meissner wrote:
On Tue, Jul 03, 2018 at 03:29:20PM +0000, Brüns, Stefan wrote:
Hi,
I would like to submit a MR for a Leap 15 package which is shared with SLE-15.
I have read https://en.opensuse.org/openSUSE:Maintenance_update_process
but obviously, the flowgraph is a dead end after the first decision ...
So, what do to in this case? File a bug report and wait for someone to pick it up?
Yes, file a bugreport... If you there is a SUSE Maintainer on it, you can also drop him/her an email with your patch or so.
I wonder, though, whether anyone can directly contribute the package fix in a form of SR. It should be possible to take a change from OBS to IBS?
Takashi
On Wed, Jul 04, 2018 at 10:52:04AM +0200, Takashi Iwai wrote:
On Wed, 04 Jul 2018 07:47:29 +0200, Marcus Meissner wrote:
On Tue, Jul 03, 2018 at 03:29:20PM +0000, Brüns, Stefan wrote:
Hi,
I would like to submit a MR for a Leap 15 package which is shared with SLE-15.
I have read https://en.opensuse.org/openSUSE:Maintenance_update_process
but obviously, the flowgraph is a dead end after the first decision ...
So, what do to in this case? File a bug report and wait for someone to pick it up?
Yes, file a bugreport... If you there is a SUSE Maintainer on it, you can also drop him/her an email with your patch or so.
I wonder, though, whether anyone can directly contribute the package fix in a form of SR. It should be possible to take a change from OBS to IBS?
It is not possible for an external contributor to submit to our internal buildservice.
A internal buildservice user can take sources via the "openSUSE.org:...obsproject" tree.
Ciao, Marcus
On Wed, 04 Jul 2018 10:54:55 +0200, Marcus Meissner wrote:
On Wed, Jul 04, 2018 at 10:52:04AM +0200, Takashi Iwai wrote:
On Wed, 04 Jul 2018 07:47:29 +0200, Marcus Meissner wrote:
On Tue, Jul 03, 2018 at 03:29:20PM +0000, Brüns, Stefan wrote:
Hi,
I would like to submit a MR for a Leap 15 package which is shared with SLE-15.
I have read https://en.opensuse.org/openSUSE:Maintenance_update_process
but obviously, the flowgraph is a dead end after the first decision ...
So, what do to in this case? File a bug report and wait for someone to pick it up?
Yes, file a bugreport... If you there is a SUSE Maintainer on it, you can also drop him/her an email with your patch or so.
I wonder, though, whether anyone can directly contribute the package fix in a form of SR. It should be possible to take a change from OBS to IBS?
It is not possible for an external contributor to submit to our internal buildservice.
A internal buildservice user can take sources via the "openSUSE.org:...obsproject" tree.
So, basically it's a style of "pull", and what we'd need is only a pull request form?
Takashi
On Jul 04 2018, Takashi Iwai tiwai@suse.de wrote:
So, basically it's a style of "pull", and what we'd need is only a pull request form?
That pull request can be written in the bugzilla entry.
Andreas.
On Wed, 04 Jul 2018 11:48:28 +0200, Andreas Schwab wrote:
On Jul 04 2018, Takashi Iwai tiwai@suse.de wrote:
So, basically it's a style of "pull", and what we'd need is only a pull request form?
That pull request can be written in the bugzilla entry.
Yes, I'm not against it, but admittedly it's old-fashioned and with a high latency when screening is involved :)
Do we have a clear procedure description somewhere?
Takashi
On Wed, 2018-07-04 at 10:52 +0200, Takashi Iwai wrote:
I wonder, though, whether anyone can directly contribute the package fix in a form of SR. It should be possible to take a change from OBS to IBS?
Sure.. all of OBS is mapped into IBS in the openSUSE.org: namespace... so a SLE-Maintainer can reuse the OBS package and do:
iosc mr openSUSE.org:home:NiceUser:branches:FOO/package SUSE:SLE-15:Update -m "Update"
(the same which is used to submit from Factory into SLE..)
Cheers Dominique
On Wednesday 2018-07-04 10:57, Dominique Leuenberger / DimStar wrote:
On Wed, 2018-07-04 at 10:52 +0200, Takashi Iwai wrote:
I wonder, though, whether anyone can directly contribute the package fix in a form of SR. It should be possible to take a change from OBS to IBS?
Sure.. all of OBS is mapped into IBS in the openSUSE.org: namespace... so a SLE-Maintainer can reuse the OBS package and do:
iosc mr openSUSE.org:home:NiceUser:branches:FOO/package SUSE:SLE-15:Update -m "Update"
How does iobs's SUSE:SLE-15 find its way back to opensuse.org?
On Jul 04 2018, Jan Engelhardt jengelh@inai.de wrote:
How does iobs's SUSE:SLE-15 find its way back to opensuse.org?
All SLE maintenance updates are copied to the corresponding update project in OBS (SUSE:SLE-15:Update) after release.
Andreas.