Buildservice - 'Submit' to Maintenance?

classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Buildservice - 'Submit' to Maintenance?

David C. Rankin
All,

  After patching gtk2 to correct the gtkrecentchooserdefault.c error corrected
in
https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7afe9cced3974f0,
when choosing submit, I get:

Unable to submit: The target project openSUSE:Leap:42.2:Update is a
maintenance release project, a submit self is not possible, please use the
maintenance workflow instead.

What does this mean? How do I submit the patch for consideration?

--
David C. Rankin, J.D.,P.E.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

Dave Plater lst


On 07/08/2017 07:12, David C. Rankin wrote:

> All,
>
>    After patching gtk2 to correct the gtkrecentchooserdefault.c error corrected
> in
> https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7afe9cced3974f0,
> when choosing submit, I get:
>
> Unable to submit: The target project openSUSE:Leap:42.2:Update is a
> maintenance release project, a submit self is not possible, please use the
> maintenance workflow instead.
>
> What does this mean? How do I submit the patch for consideration?
>
Read this link:
https://en.opensuse.org/openSUSE:Package_maintenance
Best regards
Dave P

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

David C. Rankin
On 08/07/2017 12:50 AM, Dave Plater wrote:

>
>
> On 07/08/2017 07:12, David C. Rankin wrote:
>> All,
>>
>>    After patching gtk2 to correct the gtkrecentchooserdefault.c error corrected
>> in
>> https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7afe9cced3974f0,
>>
>> when choosing submit, I get:
>>
>> Unable to submit: The target project openSUSE:Leap:42.2:Update is a
>> maintenance release project, a submit self is not possible, please use the
>> maintenance workflow instead.
>>
>> What does this mean? How do I submit the patch for consideration?
>>
> Read this link:
> https://en.opensuse.org/openSUSE:Package_maintenance
> Best regards
> Dave P
>

See; Buildservice has it out for me. I just went to work with it again and it
told me to go jump off a cliff, e.g.

This website is under heavy load (queue full)

We're sorry, too many people are accessing this website at the same time.
We're working on this problem. Please try again later.

--
David C. Rankin, J.D.,P.E.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

David C. Rankin
On 08/07/2017 01:13 AM, David C. Rankin wrote:

> On 08/07/2017 12:50 AM, Dave Plater wrote:
>>
>>
>> On 07/08/2017 07:12, David C. Rankin wrote:
>>> All,
>>>
>>>    After patching gtk2 to correct the gtkrecentchooserdefault.c error corrected
>>> in
>>> https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7afe9cced3974f0,
>>>
>>> when choosing submit, I get:
>>>
>>> Unable to submit: The target project openSUSE:Leap:42.2:Update is a
>>> maintenance release project, a submit self is not possible, please use the
>>> maintenance workflow instead.
>>>
>>> What does this mean? How do I submit the patch for consideration?
>>>
>> Read this link:
>> https://en.opensuse.org/openSUSE:Package_maintenance
>> Best regards
>> Dave P
>>
>
> See; Buildservice has it out for me. I just went to work with it again and it
> told me to go jump off a cliff, e.g.
>
> This website is under heavy load (queue full)
>
> We're sorry, too many people are accessing this website at the same time.
> We're working on this problem. Please try again later.
>

Got it:

  Created submit request 514836 to openSUSE:Maintenance:Test:Leap_42.2

--
David C. Rankin, J.D.,P.E.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

Marcus Meissner
On Mon, Aug 07, 2017 at 01:33:47AM -0500, David C. Rankin wrote:

> On 08/07/2017 01:13 AM, David C. Rankin wrote:
> > On 08/07/2017 12:50 AM, Dave Plater wrote:
> >>
> >>
> >> On 07/08/2017 07:12, David C. Rankin wrote:
> >>> All,
> >>>
> >>>    After patching gtk2 to correct the gtkrecentchooserdefault.c error corrected
> >>> in
> >>> https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7afe9cced3974f0,
> >>>
> >>> when choosing submit, I get:
> >>>
> >>> Unable to submit: The target project openSUSE:Leap:42.2:Update is a
> >>> maintenance release project, a submit self is not possible, please use the
> >>> maintenance workflow instead.
> >>>
> >>> What does this mean? How do I submit the patch for consideration?
> >>>
> >> Read this link:
> >> https://en.opensuse.org/openSUSE:Package_maintenance
> >> Best regards
> >> Dave P
> >>
> >
> > See; Buildservice has it out for me. I just went to work with it again and it
> > told me to go jump off a cliff, e.g.
> >
> > This website is under heavy load (queue full)
> >
> > We're sorry, too many people are accessing this website at the same time.
> > We're working on this problem. Please try again later.
> >
>
> Got it:
>
>   Created submit request 514836 to openSUSE:Maintenance:Test:Leap_42.2

This is the wrong target. Submit against openSUSE:Leap:42.2:Update with "osc sr",
this will rewrite the submitrequest into a maintenance request.

Ciao, Marcus

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

Marcus Meissner
In reply to this post by David C. Rankin
On Mon, Aug 07, 2017 at 01:33:47AM -0500, David C. Rankin wrote:

> On 08/07/2017 01:13 AM, David C. Rankin wrote:
> > On 08/07/2017 12:50 AM, Dave Plater wrote:
> >>
> >>
> >> On 07/08/2017 07:12, David C. Rankin wrote:
> >>> All,
> >>>
> >>>    After patching gtk2 to correct the gtkrecentchooserdefault.c error corrected
> >>> in
> >>> https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7afe9cced3974f0,
> >>>
> >>> when choosing submit, I get:
> >>>
> >>> Unable to submit: The target project openSUSE:Leap:42.2:Update is a
> >>> maintenance release project, a submit self is not possible, please use the
> >>> maintenance workflow instead.
> >>>
> >>> What does this mean? How do I submit the patch for consideration?
> >>>
> >> Read this link:
> >> https://en.opensuse.org/openSUSE:Package_maintenance
> >> Best regards
> >> Dave P
> >>
> >
> > See; Buildservice has it out for me. I just went to work with it again and it
> > told me to go jump off a cliff, e.g.
> >
> > This website is under heavy load (queue full)
> >
> > We're sorry, too many people are accessing this website at the same time.
> > We're working on this problem. Please try again later.
> >
>
> Got it:
>
>   Created submit request 514836 to openSUSE:Maintenance:Test:Leap_42.2

Also maintenance submissions need a correct changelog, use "osc vc"
Mention the opensuse bugnr, patchfilename and a short desc what it fixes.

Ciao, Marcus

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

David C. Rankin
In reply to this post by Marcus Meissner
On 08/07/2017 01:38 AM, Marcus Meissner wrote:
>> Got it:
>>
>>   Created submit request 514836 to openSUSE:Maintenance:Test:Leap_42.2
> This is the wrong target. Submit against openSUSE:Leap:42.2:Update with "osc sr",
> this will rewrite the submitrequest into a maintenance request.

OK, ..almost got it.

  I am still not sure it got submitted:

$ osc sr home:drankinatty/gtk2_patch_491d79d5 openSUSE:Leap:42.2:Update/gtk2
WARNING:
WARNING: Project does not accept submit request, request to open a NEW
maintenance incident instead
WARNING:
created request id 514841

  Did this accomplish anything? I don't see anything with 'osc my' except the
declined submittal to openSUSE:Maintenance:Test:Leap_42.2/gtk2 which is the
wrong place?

--
David C. Rankin, J.D.,P.E.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

David C. Rankin
In reply to this post by Marcus Meissner
On 08/07/2017 01:40 AM, Marcus Meissner wrote:
> Also maintenance submissions need a correct changelog, use "osc vc"
> Mention the opensuse bugnr, patchfilename and a short desc what it fixes.

Oh no. I think the osc sr did actually submit it as a maintenance request. I
included the following as the comment description:

Patched for https://bugzilla.gnome.org/show_bug.cgi?id=779605 -
gtkrecentchooser GLib-CRITICAL Source ID xxx was not found when attempting to
remove it. Gtk+2 2.24 commit
https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7afe9cced3974f0

The original bug I filed was with gnome.org, so there will not be an opensuse
bug number.

I've installed the new libgtk-2_0-0-2.24.31-13.5.1.x86_64.rpm and it works
like a champ, bug is gone when activating the gtkrecentchooser.

If I need to resubmit with 'vc' instead of 'sr', let me know. The id is
514841, but I cannot see it with 'osc my'. I don't know if that is normal or
it means that it really wasn't submitted.

--
David C. Rankin, J.D.,P.E.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

Marcus Meissner
In reply to this post by David C. Rankin
On Mon, Aug 07, 2017 at 02:28:24AM -0500, David C. Rankin wrote:

> On 08/07/2017 01:38 AM, Marcus Meissner wrote:
> >> Got it:
> >>
> >>   Created submit request 514836 to openSUSE:Maintenance:Test:Leap_42.2
> > This is the wrong target. Submit against openSUSE:Leap:42.2:Update with "osc sr",
> > this will rewrite the submitrequest into a maintenance request.
>
> OK, ..almost got it.
>
>   I am still not sure it got submitted:
>
> $ osc sr home:drankinatty/gtk2_patch_491d79d5 openSUSE:Leap:42.2:Update/gtk2
> WARNING:
> WARNING: Project does not accept submit request, request to open a NEW
> maintenance incident instead
> WARNING:
> created request id 514841
>
>   Did this accomplish anything? I don't see anything with 'osc my' except the
> declined submittal to openSUSE:Maintenance:Test:Leap_42.2/gtk2 which is the
> wrong place?

The request 514841 was created, so submission was successful.

Ciao, Marcus

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

Marcus Meissner
In reply to this post by David C. Rankin
On Mon, Aug 07, 2017 at 03:06:56AM -0500, David C. Rankin wrote:

> On 08/07/2017 01:40 AM, Marcus Meissner wrote:
> > Also maintenance submissions need a correct changelog, use "osc vc"
> > Mention the opensuse bugnr, patchfilename and a short desc what it fixes.
>
> Oh no. I think the osc sr did actually submit it as a maintenance request. I
> included the following as the comment description:
>
> Patched for https://bugzilla.gnome.org/show_bug.cgi?id=779605 -
> gtkrecentchooser GLib-CRITICAL Source ID xxx was not found when attempting to
> remove it. Gtk+2 2.24 commit
> https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7afe9cced3974f0
>
> The original bug I filed was with gnome.org, so there will not be an opensuse
> bug number.
>
> I've installed the new libgtk-2_0-0-2.24.31-13.5.1.x86_64.rpm and it works
> like a champ, bug is gone when activating the gtkrecentchooser.
>
> If I need to resubmit with 'vc' instead of 'sr', let me know. The id is
> 514841, but I cannot see it with 'osc my'. I don't know if that is normal or
> it means that it really wasn't submitted.

No, osc vc is for changelog creation and needs to be done before the submission.

It will add a gtk2.changes entry.

For tracking purposes a opensuse bug is required, even if it just points to the gnome bug.

Ciao, Marcus

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

Dave Plater lst
In reply to this post by David C. Rankin


On 07/08/2017 07:12, David C. Rankin wrote:

> All,
>
>    After patching gtk2 to correct the gtkrecentchooserdefault.c error corrected
> in
> https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7afe9cced3974f0,
> when choosing submit, I get:
>
> Unable to submit: The target project openSUSE:Leap:42.2:Update is a
> maintenance release project, a submit self is not possible, please use the
> maintenance workflow instead.
>
> What does this mean? How do I submit the patch for consideration?
>
Sorry I didn't have time to elaborate. What I normally do is ie. leap:42.3:
use osc bco -M openSUSE:Leap:42.3 gtk2 in my local obs checked out
package. That gives me a long subdirectory with the package at the end.
If the fix is in my local package then I use mc to copy the fixes over.
Then osc vc and a description of the fix mention any patches and a bug
number is mandatory for an update boo#xxxxxxx. Check in the update with
osc ci and make sure it's ok. When you "osc bco -M" it tells you how to
submit the package when it's fixed.
Hope this helps
Dave P

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

Dave Plater lst
In reply to this post by Marcus Meissner


On 07/08/2017 10:12, Marcus Meissner wrote:
> For tracking purposes a opensuse bug is required, even if it just points to the gnome bug.
>
So you need to open a bug referencing the gnome bug and after you have
submitted the update you need a needinfo in the bug for
[hidden email]
Regards
Dave P

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

David C. Rankin
On 08/07/2017 04:14 AM, Dave Plater wrote:
> So you need to open a bug referencing the gnome bug and after you have
> submitted the update you need a needinfo in the bug for [hidden email]
> Regards
> Dave P

Thank you Dave and Marcus... I think I have it down. That might be good
content for a wiki :)

--
David C. Rankin, J.D.,P.E.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

David C. Rankin
In reply to this post by Marcus Meissner
On 08/07/2017 03:12 AM, Marcus Meissner wrote:

> On Mon, Aug 07, 2017 at 03:06:56AM -0500, David C. Rankin wrote:
>> On 08/07/2017 01:40 AM, Marcus Meissner wrote:
>>> Also maintenance submissions need a correct changelog, use "osc vc"
>>> Mention the opensuse bugnr, patchfilename and a short desc what it fixes.
>>
>> Oh no. I think the osc sr did actually submit it as a maintenance request. I
>> included the following as the comment description:
>>
>> Patched for https://bugzilla.gnome.org/show_bug.cgi?id=779605 -
>> gtkrecentchooser GLib-CRITICAL Source ID xxx was not found when attempting to
>> remove it. Gtk+2 2.24 commit
>> https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7afe9cced3974f0
>>
>> The original bug I filed was with gnome.org, so there will not be an opensuse
>> bug number.
>>
>> I've installed the new libgtk-2_0-0-2.24.31-13.5.1.x86_64.rpm and it works
>> like a champ, bug is gone when activating the gtkrecentchooser.
>>
>> If I need to resubmit with 'vc' instead of 'sr', let me know. The id is
>> 514841, but I cannot see it with 'osc my'. I don't know if that is normal or
>> it means that it really wasn't submitted.
>
> No, osc vc is for changelog creation and needs to be done before the submission.
>
> It will add a gtk2.changes entry.
>
> For tracking purposes a opensuse bug is required, even if it just points to the gnome bug.
>
> Ciao, Marcus
>

I still have no idea if this actually worked.

I filed opensuse bug:

https://bugzilla.opensuse.org/show_bug.cgi?id=1052668

I used

  $ osc vc and added to gtk2.changes the following:

-------------------------------------------------------------------
Tue Aug  8 23:08:00 UTC 2017 - [hidden email]

- Fix gtkrecentchooser GLib-CRITICAL Source ID xxx was not found:
  + Bug 1052668.

I used

  $ osc sr home:drankinatty/gtk2_patch_491d79d5 openSUSE:Leap:42.2:Update/gtk2

added when prompted for comment:

OpenSuSE bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1052668. Patched
for https://bugzilla.gnome.org/show_bug.cgi?id=779605 - gtkrecentchooser
GLib-CRITICAL Source ID xxx was not found when attempting to remove it. Gtk+2
2.24 commit
https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7afe9cced3974f0

output:

WARNING:
WARNING: Project does not accept submit request, request to open a NEW
maintenance incident instead
WARNING:
created request id 515110

I guess it is too soon for osc my to show anything about 515110, all I see is:

$ osc my
Declined requests created by you (revoke, reopen or supersede):

514841  State:declined   By:AndreasStieger When:2017-08-07T12:55:45
        maintenance_incident:
home:drankinatty/gtk2_patch_491d79d5@8b1c601bb24ab61845738d1c96a97ea3 ->
openSUSE:Maintenance (release in openSUSE:Leap:42.2:Update)
        Review by User       is accepted:  maintbot(maintbot)
        Descr: Patched for https://bugzilla.gnome.org/show_bug.cgi?id=779605 -
               gtkrecentchooser GLib-CRITICAL Source ID xxx was not found when
               attempting to remove it. Gtk+2 2.24 commit https://git.gnome.org/
               browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7a
               fe9cced3974f0
        Comment: See https://bugzilla.opensuse.org/show_bug.cgi?id=1052570

514836  State:declined   By:msmeissn     When:2017-08-07T06:37:28
        submit:          home:drankinatty/gtk2_patch_491d79d5@4 ->
openSUSE:Maintenance:Test:Leap_42.2/gtk2
        Descr: Patched for https://bugzilla.gnome.org/show_bug.cgi?id=779605 -
               gtkrecentchooser GLib-CRITICAL Source ID xxx was not found when
               attempting to remove it. Gtk+2 2.24 commit https://git.gnome.org/
               browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7afe9c
               ced3974f0
        Comment: see email

So now do we just wait and see?

This was a heck of a process. I still don't know why I can choose 'Submit' in
my buildservice package and have it do the same thing rather than having to
use osc. I guess that will become clearer as I get more familiar with it, but
at this point, I still feel like a fish-out-of-water with this whole
newfangled process.

(which is not entirely uncommon for any newfangled process)

--
David C. Rankin, J.D.,P.E.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

David C. Rankin
In reply to this post by Dave Plater lst
On 08/07/2017 04:08 AM, Dave Plater wrote:

> Sorry I didn't have time to elaborate. What I normally do is ie. leap:42.3:
> use osc bco -M openSUSE:Leap:42.3 gtk2 in my local obs checked out package.
> That gives me a long subdirectory with the package at the end.
> If the fix is in my local package then I use mc to copy the fixes over.
> Then osc vc and a description of the fix mention any patches and a bug number
> is mandatory for an update boo#xxxxxxx. Check in the update with osc ci and
> make sure it's ok. When you "osc bco -M" it tells you how to submit the
> package when it's fixed.
> Hope this helps
> Dave P

  Hehe... Thanks, no problem, I like the "groping around in the dark" feeling.
I think I have it sorted. (maybe not - see other post).

  What made this so darn frustrating is for 15 years it has been [patch,
rpmbuild -ba whatever.spec, (all good!|damn!, redo...)?, attach to bug
report], then for (5, 6, 7?) years it has been, "No use build service and
branch the package" (which I dutifully did only to find "Submit" won't work),
and now it is "well -- use osc instead of buildservice", Wow?

  Complicating the process was I filed the bug upstream with
bugzilla.gnome.org which was fixed and committed directly to gtk+2.24.31, so I
created a patch for both the Arch PKGBUILD, and the opensuse gtk2.spec and
successfully built in buildservice for 13.2, and Leap 42.2 (the 13.1 and
Tumbleweed builds will need further tweaks, probably either gtk2 version
related or glib related). So no opensuse bug was ever opened, and I guess I
was just too dense to know that was an osc requirement. (I do now... :)

  So what I envisioned taking 15 minutes for the branch/patch and build to
complete and a 2-sec click-Submit has taken more than a day. (with the
fringe-benefit of progressing to the knowledge level with osc in the wonderful
world of cognitive taxonomy...)

  I guess it's better than being Paul and jacking with SCSI terminations on
tape drives.... :)

--
David C. Rankin, J.D.,P.E.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

Dave Plater lst
In reply to this post by David C. Rankin


On 08/08/2017 06:16, David C. Rankin wrote:
> o now do we just wait and see?
>
> This was a heck of a process. I still don't know why I can choose 'Submit' in
> my buildservice package and have it do the same thing rather than having to
> use osc. I guess that will become clearer as I get more familiar with it, but
> at this point, I still feel like a fish-out-of-water with this whole
> newfangled process.
>
> (which is not entirely uncommon for any newfangled process)
The request exists but you should have osc sr -M or osc mr and you have
to create a needinfo in the bug from maintenance.
Dave P

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

Dave Plater lst
In reply to this post by David C. Rankin


On 08/08/2017 06:16, David C. Rankin wrote:
> o now do we just wait and see?
>
> This was a heck of a process. I still don't know why I can choose 'Submit' in
> my buildservice package and have it do the same thing rather than having to
> use osc. I guess that will become clearer as I get more familiar with it, but
> at this point, I still feel like a fish-out-of-water with this whole
> newfangled process.
>
> (which is not entirely uncommon for any newfangled process)
Another point, we don't normally use full urls for openSUSE bugs only
boo#bugnumber is needed.
The osc vc changes entry you made didn't appear in the package you
submitted.
Regards
Dave P

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

David C. Rankin
In reply to this post by David C. Rankin
On 08/07/2017 11:16 PM, David C. Rankin wrote:

> On 08/07/2017 03:12 AM, Marcus Meissner wrote:
>> On Mon, Aug 07, 2017 at 03:06:56AM -0500, David C. Rankin wrote:
>>> On 08/07/2017 01:40 AM, Marcus Meissner wrote:
>>>> Also maintenance submissions need a correct changelog, use "osc vc"
>>>> Mention the opensuse bugnr, patchfilename and a short desc what it fixes.
>>>
>>> Oh no. I think the osc sr did actually submit it as a maintenance request. I
>>> included the following as the comment description:
>>>
>>> Patched for https://bugzilla.gnome.org/show_bug.cgi?id=779605 -
>>> gtkrecentchooser GLib-CRITICAL Source ID xxx was not found when attempting to
>>> remove it. Gtk+2 2.24 commit
>>> https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7afe9cced3974f0
>>>
>>> The original bug I filed was with gnome.org, so there will not be an opensuse
>>> bug number.
>>>
>>> I've installed the new libgtk-2_0-0-2.24.31-13.5.1.x86_64.rpm and it works
>>> like a champ, bug is gone when activating the gtkrecentchooser.
>>>
>>> If I need to resubmit with 'vc' instead of 'sr', let me know. The id is
>>> 514841, but I cannot see it with 'osc my'. I don't know if that is normal or
>>> it means that it really wasn't submitted.
>>
>> No, osc vc is for changelog creation and needs to be done before the submission.
>>
>> It will add a gtk2.changes entry.
>>
>> For tracking purposes a opensuse bug is required, even if it just points to the gnome bug.
>>
>> Ciao, Marcus
>>
>
> I still have no idea if this actually worked.
>
> I filed opensuse bug:
>
> https://bugzilla.opensuse.org/show_bug.cgi?id=1052668
>
> I used
>
>   $ osc vc and added to gtk2.changes the following:
>
> -------------------------------------------------------------------
> Tue Aug  8 23:08:00 UTC 2017 - [hidden email]
>
> - Fix gtkrecentchooser GLib-CRITICAL Source ID xxx was not found:
>   + Bug 1052668.
>
> I used
>
>   $ osc sr home:drankinatty/gtk2_patch_491d79d5 openSUSE:Leap:42.2:Update/gtk2
>
> added when prompted for comment:
>
> OpenSuSE bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1052668. Patched
> for https://bugzilla.gnome.org/show_bug.cgi?id=779605 - gtkrecentchooser
> GLib-CRITICAL Source ID xxx was not found when attempting to remove it. Gtk+2
> 2.24 commit
> https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7afe9cced3974f0
>
> output:
>
> WARNING:
> WARNING: Project does not accept submit request, request to open a NEW
> maintenance incident instead
> WARNING:
> created request id 515110
>
> I guess it is too soon for osc my to show anything about 515110, all I see is:
>
> $ osc my
> Declined requests created by you (revoke, reopen or supersede):
>
> 514841  State:declined   By:AndreasStieger When:2017-08-07T12:55:45
>         maintenance_incident:
> home:drankinatty/gtk2_patch_491d79d5@8b1c601bb24ab61845738d1c96a97ea3 ->
> openSUSE:Maintenance (release in openSUSE:Leap:42.2:Update)
>         Review by User       is accepted:  maintbot(maintbot)
>         Descr: Patched for https://bugzilla.gnome.org/show_bug.cgi?id=779605 -
>                gtkrecentchooser GLib-CRITICAL Source ID xxx was not found when
>                attempting to remove it. Gtk+2 2.24 commit https://git.gnome.org/
>                browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7a
>                fe9cced3974f0
>         Comment: See https://bugzilla.opensuse.org/show_bug.cgi?id=1052570
>
> 514836  State:declined   By:msmeissn     When:2017-08-07T06:37:28
>         submit:          home:drankinatty/gtk2_patch_491d79d5@4 ->
> openSUSE:Maintenance:Test:Leap_42.2/gtk2
>         Descr: Patched for https://bugzilla.gnome.org/show_bug.cgi?id=779605 -
>                gtkrecentchooser GLib-CRITICAL Source ID xxx was not found when
>                attempting to remove it. Gtk+2 2.24 commit https://git.gnome.org/
>                browse/gtk+/commit/?h=gtk-2-24&id=491d79d54083044a5de3bfa2d7afe9c
>                ced3974f0
>         Comment: see email
>
> So now do we just wait and see?
>
> This was a heck of a process. I still don't know why I can choose 'Submit' in
> my buildservice package and have it do the same thing rather than having to
> use osc. I guess that will become clearer as I get more familiar with it, but
> at this point, I still feel like a fish-out-of-water with this whole
> newfangled process.
>
> (which is not entirely uncommon for any newfangled process)
>

Perhaps 4th try will be the charm?

$ osc sr home:drankinatty/gtk2_patch_491d79d5 openSUSE:Leap:42.2:Update/gtk2
WARNING:
WARNING: Project does not accept submit request, request to open a NEW
maintenance incident instead
WARNING:
created request id 515113

Attempted to sumbit after update up buildservice gtk2.change to SLE per
Andreas Stieger but buildservice would not submit against SLE, e.g.

Unable to submit: The target project SUSE:SLE-12:Update is a maintenance
release project, a submit self is not possible, please use the maintenance
workflow instead.

Attempting again after .change update on buildservice to Leap:42.2 as it is
unclear which SLE will accept the maintenance request.

This just keeps getting easier....

--
David C. Rankin, J.D.,P.E.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

David C. Rankin
In reply to this post by Dave Plater lst
On 08/08/2017 12:27 AM, Dave Plater wrote:
> The request exists but you should have osc sr -M or osc mr and you have to
> create a needinfo in the bug from maintenance.
> Dave P

Thanks Dave,

  The -M and mr committed to memory (and if they become needed for the 5th try...)

--
David C. Rankin, J.D.,P.E.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Buildservice - 'Submit' to Maintenance?

Dave Plater lst
In reply to this post by David C. Rankin


On 08/08/2017 07:39, David C. Rankin wrote:
> Attempting again after .change update on buildservice to Leap:42.2 as it is
> unclear which SLE will accept the maintenance request.
>
> This just keeps getting easier....
>
You didn't use -M again, if you're doing multiple openSUSE version
updates the you use the osc mbranch command. I learned all this from the
wiki link I gave you and trial and error. You can then fix the different
(SLE 42.2 42.3) packages with the patch and changes entries and use osc
mr from the project root directory.

Dave P

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

12