Re: when will bodhi (updates) recognize fc31/f31 updates
On Thu, 15 Aug 2019 at 22:33, Kevin Fenzi wrote: > > On 8/15/19 7:44 AM, Alexander Bokovoy wrote: > > On to, 15 elo 2019, Kaleb Keithley wrote: > >> On Thu, Aug 15, 2019 at 10:21 AM Alexander Bokovoy > >> wrote: > >> > >>> On to, 15 elo 2019, Kaleb Keithley wrote: > >>> >I've tried to submit a build on f31 to testing, using both the cli > >>> and via > >>> >the web site, and both are failing > >>> > > >>> >On the web site I get a popup with: Builds : Cannot find release > >>> associated > >>> >with build: nfs-ganesha-2.8.2-5.fc31, tags: ['f31'] > >>> > > >>> >fedpkg update gets: Could not execute update: Could not generate update > >>> >request: Cannot find release associated with build: > >>> >nfs-ganesha-2.8.2-5.fc31, tags: ['f31'] > >>> My understanding is that F31 doesn't need bodhi right now -- all > >>> packages built for it appear in the distro, as with rawhide before. > >>> > >>> Branched will get bodhi activated later this month. > >>> > >> > >> Well, it's confusing (to me anyway), because before branching, new > >> f31/rawhide builds showed up automatically as "stable" in bodhi. > >> > >> And now new f32/rawhide builds show up automatically as "stable." > >> > >> Making me wonder what is status of the new f31 build(s) I've just done? > >> They don't show up in bodhi at all. > > Yes, Bodhi activation for a Branched is marked in the schedule > > separately. This was noted in the mass branching email: > > > > -- > > Bodhi is currently not active for Fedora 31, it will be enabled in > > couple of weeks time when we hit Beta change freeze point in the Fedora > > 31 schedule[1]. > > > > [1] https://fedoraproject.org/wiki/Releases/31/Schedule > > -- > > > > A confusion is probably because at the same time Gating in Rawhide was > > introduced. Gating in Rawhide relies on Bodhi, so there is Bodhi for > > F32. I think we could have made Bodhi for F31 with automated acceptance > > of the packages more visible but it might have been postponed to the > > "Bodhi activation point" altogether. > > Yeah, it's been confusing for sure. :( > > Right now rawhide (f32) is doing gating as it was before. > > Branched (f31) is acting like rawhide used to, pre gating (ie, builds > are just signed and added) I just opened a PR to the releng SOP (https://pagure.io/releng/pull-request/8651), so that the branched release (f31) behave like rawhide in bodhi (Gated) until we activate it properly (2 weeks after branching). > > I would expect branched to also do gating, so I think we should move it > to that. > > Or, we could just decide to enable bodhi for good at branching. The > reason we didn't do this before was that its more stuff for releng to > deal with at branching, and the 2 weeks give people time to get builds > in fast to finish up things they know for sure they want to get into the > branched release. It might just be a lot less confusing to enable it tho. > > kevin > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Re: when will bodhi (updates) recognize fc31/f31 updates
On 8/15/19 7:44 AM, Alexander Bokovoy wrote: > On to, 15 elo 2019, Kaleb Keithley wrote: >> On Thu, Aug 15, 2019 at 10:21 AM Alexander Bokovoy >> wrote: >> >>> On to, 15 elo 2019, Kaleb Keithley wrote: >>> >I've tried to submit a build on f31 to testing, using both the cli >>> and via >>> >the web site, and both are failing >>> > >>> >On the web site I get a popup with: Builds : Cannot find release >>> associated >>> >with build: nfs-ganesha-2.8.2-5.fc31, tags: ['f31'] >>> > >>> >fedpkg update gets: Could not execute update: Could not generate update >>> >request: Cannot find release associated with build: >>> >nfs-ganesha-2.8.2-5.fc31, tags: ['f31'] >>> My understanding is that F31 doesn't need bodhi right now -- all >>> packages built for it appear in the distro, as with rawhide before. >>> >>> Branched will get bodhi activated later this month. >>> >> >> Well, it's confusing (to me anyway), because before branching, new >> f31/rawhide builds showed up automatically as "stable" in bodhi. >> >> And now new f32/rawhide builds show up automatically as "stable." >> >> Making me wonder what is status of the new f31 build(s) I've just done? >> They don't show up in bodhi at all. > Yes, Bodhi activation for a Branched is marked in the schedule > separately. This was noted in the mass branching email: > > -- > Bodhi is currently not active for Fedora 31, it will be enabled in > couple of weeks time when we hit Beta change freeze point in the Fedora > 31 schedule[1]. > > [1] https://fedoraproject.org/wiki/Releases/31/Schedule > -- > > A confusion is probably because at the same time Gating in Rawhide was > introduced. Gating in Rawhide relies on Bodhi, so there is Bodhi for > F32. I think we could have made Bodhi for F31 with automated acceptance > of the packages more visible but it might have been postponed to the > "Bodhi activation point" altogether. Yeah, it's been confusing for sure. :( Right now rawhide (f32) is doing gating as it was before. Branched (f31) is acting like rawhide used to, pre gating (ie, builds are just signed and added) I would expect branched to also do gating, so I think we should move it to that. Or, we could just decide to enable bodhi for good at branching. The reason we didn't do this before was that its more stuff for releng to deal with at branching, and the 2 weeks give people time to get builds in fast to finish up things they know for sure they want to get into the branched release. It might just be a lot less confusing to enable it tho. kevin signature.asc Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Re: when will bodhi (updates) recognize fc31/f31 updates
On to, 15 elo 2019, Kaleb Keithley wrote: On Thu, Aug 15, 2019 at 10:21 AM Alexander Bokovoy wrote: On to, 15 elo 2019, Kaleb Keithley wrote: >I've tried to submit a build on f31 to testing, using both the cli and via >the web site, and both are failing > >On the web site I get a popup with: Builds : Cannot find release associated >with build: nfs-ganesha-2.8.2-5.fc31, tags: ['f31'] > >fedpkg update gets: Could not execute update: Could not generate update >request: Cannot find release associated with build: >nfs-ganesha-2.8.2-5.fc31, tags: ['f31'] My understanding is that F31 doesn't need bodhi right now -- all packages built for it appear in the distro, as with rawhide before. Branched will get bodhi activated later this month. Well, it's confusing (to me anyway), because before branching, new f31/rawhide builds showed up automatically as "stable" in bodhi. And now new f32/rawhide builds show up automatically as "stable." Making me wonder what is status of the new f31 build(s) I've just done? They don't show up in bodhi at all. Yes, Bodhi activation for a Branched is marked in the schedule separately. This was noted in the mass branching email: -- Bodhi is currently not active for Fedora 31, it will be enabled in couple of weeks time when we hit Beta change freeze point in the Fedora 31 schedule[1]. [1] https://fedoraproject.org/wiki/Releases/31/Schedule -- A confusion is probably because at the same time Gating in Rawhide was introduced. Gating in Rawhide relies on Bodhi, so there is Bodhi for F32. I think we could have made Bodhi for F31 with automated acceptance of the packages more visible but it might have been postponed to the "Bodhi activation point" altogether. -- / Alexander Bokovoy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Re: when will bodhi (updates) recognize fc31/f31 updates
On Thu, Aug 15, 2019 at 10:21 AM Alexander Bokovoy wrote: > On to, 15 elo 2019, Kaleb Keithley wrote: > >I've tried to submit a build on f31 to testing, using both the cli and via > >the web site, and both are failing > > > >On the web site I get a popup with: Builds : Cannot find release > associated > >with build: nfs-ganesha-2.8.2-5.fc31, tags: ['f31'] > > > >fedpkg update gets: Could not execute update: Could not generate update > >request: Cannot find release associated with build: > >nfs-ganesha-2.8.2-5.fc31, tags: ['f31'] > My understanding is that F31 doesn't need bodhi right now -- all > packages built for it appear in the distro, as with rawhide before. > > Branched will get bodhi activated later this month. > Well, it's confusing (to me anyway), because before branching, new f31/rawhide builds showed up automatically as "stable" in bodhi. And now new f32/rawhide builds show up automatically as "stable." Making me wonder what is status of the new f31 build(s) I've just done? They don't show up in bodhi at all. -- Kaleb ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Re: when will bodhi (updates) recognize fc31/f31 updates
On to, 15 elo 2019, Kaleb Keithley wrote: I've tried to submit a build on f31 to testing, using both the cli and via the web site, and both are failing On the web site I get a popup with: Builds : Cannot find release associated with build: nfs-ganesha-2.8.2-5.fc31, tags: ['f31'] fedpkg update gets: Could not execute update: Could not generate update request: Cannot find release associated with build: nfs-ganesha-2.8.2-5.fc31, tags: ['f31'] My understanding is that F31 doesn't need bodhi right now -- all packages built for it appear in the distro, as with rawhide before. Branched will get bodhi activated later this month. -- / Alexander Bokovoy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
