Error with fedpkg update

[Gerald B. Cox]

I've been trying to submit an update to testing for several days now and it
keeps failing
with the following message:

Could not execute update: Could not generate update request: Cannot find
release associated with build: copyq-3.9.1-1.fc31, tags: ['f31']
A copy of the filled in template is saved as bodhi.template.last

The fedpkg build was successful, and I see it in koj.

Does anyone have an idea to what the problem is?

Thanks!

[Fabio Valentini]

On Fri, Aug 23, 2019 at 4:18 PM Gerald B. Cox <gbcox(a)bzb.us&gt; wrote:
>  I've been trying to submit an update to testing for several days now and it keeps
> failing
>  with the following message:
>
>  Could not execute update: Could not generate update request: Cannot find release
> associated with build: copyq-3.9.1-1.fc31, tags: ['f31']
>  A copy of the filled in template is saved as bodhi.template.last
>
>  The fedpkg build was successful, and I see it in koj.
>
>  Does anyone have an idea to what the problem is? 
bodhi is not yet enabled for fedora 31.

According to the schedule, that's supposed to happen on 2019-08-29:
https://fedoraproject.org/wiki/Releases/31/Schedule

Fabio

> Thanks!
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]

[Adam Williamson]

On Fri, 2019-08-23 at 16:20 +0200, Fabio Valentini wrote:
>  On Fri, Aug 23, 2019 at 4:18 PM Gerald B. Cox <gbcox(a)bzb.us&gt;
> wrote:
>  > I've been trying to submit an update to testing for several days now and it
> keeps failing
>  > with the following message:
>  > 
>  > Could not execute update: Could not generate update request: Cannot find release
> associated with build: copyq-3.9.1-1.fc31, tags: ['f31']
>  > A copy of the filled in template is saved as bodhi.template.last
>  > 
>  > The fedpkg build was successful, and I see it in koj.
>  > 
>  > Does anyone have an idea to what the problem is?
>  
>  bodhi is not yet enabled for fedora 31.
>  
>  According to the schedule, that's supposed to happen on 2019-08-29:
>  https://fedoraproject.org/wiki/Releases/31/Schedule 
And just to be clear - that means you don't *need* to create an update.
Your build just gets tagged into f31 automatically.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

[Gerald B. Cox]

On Fri, Aug 23, 2019 at 1:49 PM Adam Williamson <adamwill(a)fedoraproject.org&gt;
wrote:

>  >
>  > bodhi is not yet enabled for fedora 31.
>  >
>  > According to the schedule, that's supposed to happen on 2019-08-29:
>  > https://fedoraproject.org/wiki/Releases/31/Schedule
>
>  And just to be clear - that means you don't *need* to create an update.
>  Your build just gets tagged into f31 automatically.
>
>  
I'm a bit confused.  The master build went to F32 (rawhide).  So I then
built for F31, F30 and F29.  Now F32 build is showing a status of "Stable"
in bodhi, F29 and F30 are showing "testing".  So you're saying that
automagically F31 will appear in bodhi as "stable"?

[Adam Williamson]

On Fri, 2019-08-23 at 14:54 -0300, Gerald B. Cox wrote:
>  On Fri, Aug 23, 2019 at 1:49 PM Adam Williamson
> <adamwill(a)fedoraproject.org&gt;
>  wrote:
>  
>  > > bodhi is not yet enabled for fedora 31.
>  > > 
>  > > According to the schedule, that's supposed to happen on 2019-08-29:
>  > > https://fedoraproject.org/wiki/Releases/31/Schedule
>  > 
>  > And just to be clear - that means you don't *need* to create an update.
>  > Your build just gets tagged into f31 automatically.
>  > 
>  > 
>  I'm a bit confused.  The master build went to F32 (rawhide).  So I then
>  built for F31, F30 and F29.  Now F32 build is showing a status of "Stable"
>  in bodhi, F29 and F30 are showing "testing".  So you're saying that
>  automagically F31 will appear in bodhi as "stable"? 
It won't appear in Bodhi at all, but it will get the koji tag 'f31' and
so appear in Fedora 31 composes.

This is how Rawhide and Branched-pre-Bodhi-enablement *always* worked -
it just feels a bit odd now because we have the gating stuff enabled
for Rawhide, but it wasn't set up for the short time between Branch
point and Bodhi enablement for the branch; so right now Rawhide is
working the 'new' way with auto-created Bodhi updates, but F31 is
working the 'old' way with no Bodhi at all.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

[Kevin Fenzi]

On 8/23/19 11:10 AM, Adam Williamson wrote:
>  
>  It won't appear in Bodhi at all, but it will get the koji tag 'f31' and
>  so appear in Fedora 31 composes.
>  
>  This is how Rawhide and Branched-pre-Bodhi-enablement *always* worked -
>  it just feels a bit odd now because we have the gating stuff enabled
>  for Rawhide, but it wasn't set up for the short time between Branch
>  point and Bodhi enablement for the branch; so right now Rawhide is
>  working the 'new' way with auto-created Bodhi updates, but F31 is
>  working the 'old' way with no Bodhi at all. 
NOTE: for next branching I think the idea is to enable gating for it as
well as rawhide. This will be less confusing for everyone and make more
sense... we just weren't ready for it this time.

kevin

[Gerald B. Cox]

Guys, I'm still getting this message:
fedpkg update
Could not execute update: Could not generate update request: Cannot find
release associated with build: copyq-3.9.2-1.fc31, tags: ['f31']
A copy of the filled in template is saved as bodhi.template.last

I just checked bodhi and other packages are being accepted for testing for
f31.  What is going on?



On Fri, Aug 23, 2019 at 12:20 PM Kevin Fenzi <kevin(a)scrye.com&gt; wrote:

>  On 8/23/19 11:10 AM, Adam Williamson wrote:
>  >
>  > It won't appear in Bodhi at all, but it will get the koji tag 'f31' and
>  > so appear in Fedora 31 composes.
>  >
>  > This is how Rawhide and Branched-pre-Bodhi-enablement *always* worked -
>  > it just feels a bit odd now because we have the gating stuff enabled
>  > for Rawhide, but it wasn't set up for the short time between Branch
>  > point and Bodhi enablement for the branch; so right now Rawhide is
>  > working the 'new' way with auto-created Bodhi updates, but F31 is
>  > working the 'old' way with no Bodhi at all.
>
>  NOTE: for next branching I think the idea is to enable gating for it as
>  well as rawhide. This will be less confusing for everyone and make more
>  sense... we just weren't ready for it this time.
>
>  kevin
>
>
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>

[Adam Williamson]

On Thu, 2019-08-29 at 07:56 -0700, Gerald B. Cox wrote:
>  Guys, I'm still getting this message:
>  fedpkg update
>  Could not execute update: Could not generate update request: Cannot find
>  release associated with build: copyq-3.9.2-1.fc31, tags: ['f31']
>  A copy of the filled in template is saved as bodhi.template.last 
I mean, as a simple fix why not just bump it and do a -2 build and see
if you can send an update for that?
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

[Gerald B. Cox]

If I do that, I believe I get into a situation where the other builds f29,
f30 and F32 are behind, which if I remember correctly causes other issues -
and shouldn't we understand what is wrong with the system rather than just
trying to hack around it?

On Thu, Aug 29, 2019 at 12:17 PM Adam Williamson <adamwill(a)fedoraproject.org&gt;
wrote:

>  On Thu, 2019-08-29 at 07:56 -0700, Gerald B. Cox wrote:
>  > Guys, I'm still getting this message:
>  > fedpkg update
>  > Could not execute update: Could not generate update request: Cannot find
>  > release associated with build: copyq-3.9.2-1.fc31, tags: ['f31']
>  > A copy of the filled in template is saved as bodhi.template.last
>
>  I mean, as a simple fix why not just bump it and do a -2 build and see
>  if you can send an update for that?
>  --
>  Adam Williamson
>  Fedora QA Community Monkey
>  IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
>  http://www.happyassassin.net
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>

[Iñaki Ucar]

On Thu, 29 Aug 2019 at 17:36, Gerald B. Cox <gbcox(a)bzb.us&gt; wrote:
>  If I do that, I believe I get into a situation where the other builds f29, f30 and F32
> are behind, which if I remember correctly causes other issues - and shouldn't we
> understand what is wrong with the system rather than just trying to hack around it?
copyq was in the Fedora 31 compose report three days ago:

https://lists.fedoraproject.org/archives/list/[e-mail].o...

Iñaki

[Gerald B. Cox]

Thanks all for the replies... I was under the impression from the previous
response I needed to submit to bodhi, but I believe I misinterpreted and
that was intended for future changes going forward.  Looking at bodhi now
it's a little confusing seeing f29, f30 and f32 there but no f31.

On Thu, Aug 29, 2019 at 12:52 PM Iñaki Ucar <iucar(a)fedoraproject.org&gt; wrote:

>  On Thu, 29 Aug 2019 at 17:36, Gerald B. Cox <gbcox(a)bzb.us&gt;
> wrote:
>  >
>  > If I do that, I believe I get into a situation where the other builds
>  f29, f30 and F32 are behind, which if I remember correctly causes other
>  issues - and shouldn't we understand what is wrong with the system rather
>  than just trying to hack around it?
>
>  copyq was in the Fedora 31 compose report three days ago:
>
>
>
> https://lists.fedoraproject.org/archives/list/[e-mail].o...
>
>  Iñaki
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>

[Iñaki Ucar]

On Thu, 29 Aug 2019 at 18:06, Gerald B. Cox <gbcox(a)bzb.us&gt; wrote:
>  Thanks all for the replies... I was under the impression from the previous response I
> needed to submit to bodhi, but I believe I misinterpreted and that was intended for future
> changes going forward.  Looking at bodhi now it's a little confusing seeing f29, f30
> and f32 there but no f31. 
Yeap, it's confusing because Bodhi shows pre-branching and
post-activation updates. But every build between those two dates
directly landed in f31 stable, as always, including your package. :)

Iñaki

[Fabio Valentini]

On Fri, Aug 23, 2019 at 7:58 PM Gerald B. Cox <gbcox(a)bzb.us&gt; wrote:
>  On Fri, Aug 23, 2019 at 1:49 PM Adam Williamson <adamwill(a)fedoraproject.org&gt;
> wrote:
> >
> >
> > >
> > > bodhi is not yet enabled for fedora 31.
> > >
> > > According to the schedule, that's supposed to happen on 2019-08-29:
> > > https://fedoraproject.org/wiki/Releases/31/Schedule
> >
> > And just to be clear - that means you don't *need* to create an update.
> > Your build just gets tagged into f31 automatically.
> >
>
>  I'm a bit confused.  The master build went to F32 (rawhide).  So I then built for
> F31, F30 and F29.  Now F32 build is showing a status of "Stable" in bodhi, F29
> and F30 are showing "testing".  So you're saying that automagically F31 will
> appear in bodhi as "stable"? 
No, F31 builds won't show up in bodhi at all. They go directly to
"stable" in koji. Updates only show up for F32 because of rawhide
gating, which automatically submits packages through bodhi for
testing. However, that's not yet implemented / enabled for branched
releases.

Still, bodhi *will* be activated for branched / F31 next week, and
then you will have to manually submit bodhi updates for F31 - as
usual.

TL;DR: The procedure for branched has not changed at all. It's just
that rawhide gating and rawhide / F32 updates automagically showing up
in bodhi probably makes things confusing.

Fabio

> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]