2:28 p.m.
Hi All,
Fedora 36 has now been branched, please be sure to do a git pull
--rebase to pick up the new branch, as an additional reminder
rawhide/f36 has been completely isolated from previous releases, so
this means that anything you do for f36 you also have to do in the
rawhide branch and do a build there. There will be a Fedora 36 compose
and it'll appear in
http://dl.fedoraproject.org/pub/fedora/linux/development/36/ once
complete. Please be sure to check it out. Bodhi is currently not
active for Fedora 36, it will be enabled in a couple of weeks when we
hit Beta change freeze point in the Fedora 36 schedule[1].
Two things to remember:
1. The modules will be built for a new platform:f37
2. The signing of RPMs is not done yet with the new f37 key.
3. F36/branched release is frozen right now until we get a successful
compose, expect that your f36 builds won't be available immediately.
Thanks for understanding.
[1] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html
--
Tomas Hrcka
role: CPE Team - Senior Software Engineer
fas: humaton
libera.CHAT: jednorozec
_______________________________________________
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-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/devel-announce@lists.fedora...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
5:53 p.m.
On Tue, Feb 08, 2022 at 09:28:53PM +0100, Tomas Hrcka wrote:
Hi All,
Fedora 36 has now been branched, please be sure to do a git pull
--rebase to pick up the new branch, as an additional reminder
Most of my packages appear to have f36 branches, but of the two new
packages I just requested yesterday,
- the_foundation has a f36 branch
- lagrange doesn't
Should I just request it manually?
Thanks,
--
Michel Alexandre Salim
identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2
6:06 p.m.
On Tue, 2022-02-08 at 21:28 +0100, Tomas Hrcka wrote:
Bodhi is currently not
active for Fedora 36, it will be enabled in a couple of weeks when we
hit Beta change freeze point in the Fedora 36 schedule[1].
We should update this boilerplate (I'm assuming this email is
copy/pasted from release to release), as it's not accurate any more.
Bodhi *is* active for F36 (and has been for some time). For the next
couple of weeks the policy for branched F36 will be the same as for
Rawhide: no manual feedback or wait period is needed for updates to go
stable. Greenwave gating is applied, though, so if your package has a
gating policy, updates for it may be gated just as for Rawhide.
I will turn on openQA testing for Branched once branching is complete
and settled, and enable the critpath gating policies for F36, so
critpath updates which fail openQA testing will be gated.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
6:30 p.m.
On Tue, Feb 08, 2022 at 03:53:51PM -0800, Michel Alexandre Salim wrote:
On Tue, Feb 08, 2022 at 09:28:53PM +0100, Tomas Hrcka wrote:
> Hi All,
>
> Fedora 36 has now been branched, please be sure to do a git pull
> --rebase to pick up the new branch, as an additional reminder
Most of my packages appear to have f36 branches, but of the two new
packages I just requested yesterday,
- the_foundation has a f36 branch
- lagrange doesn't
Should I just request it manually?
Yep.
kevin
6:42 p.m.
One of my packages ("blueman") had a new release today, so I updated it.
Despite me committing to the rawhide branch, the build was given the ".f36"
suffix,
so when I pushed to the f36 branch and tried to build the package,
koji berated me that it's been already built.
So what now? Should I just tag the build manually (using the "f36" tag?)
and submit a bodhi update for F36?
A.FI.
7:32 p.m.
On Wed, Feb 09, 2022 at 12:42:25AM -0000, Artur Frenszek-Iwicki wrote:
One of my packages ("blueman") had a new release today, so
I updated it.
Despite me committing to the rawhide branch, the build was given the ".f36"
suffix,
so when I pushed to the f36 branch and tried to build the package,
koji berated me that it's been already built.
yep.
So what now? Should I just tag the build manually (using the
"f36" tag?)
and submit a bodhi update for F36?
Easiest and most clear would be to just bump and rebuild in rawhide (it
will get .fc37 dist), then merge that to f36 branch and build there.
And I suppose we should really look at disabling builds on mass branch
day (while it's happening) it never ends well. :)
kevin
2:39 a.m.
On Wed, Feb 9, 2022 at 2:32 AM Kevin Fenzi <kevin(a)scrye.com> wrote:
And I suppose we should really look at disabling builds on mass branch
day (while it's happening) it never ends well. :)
Should I open a FESCo / Releng / Infra ticket for this, so we can at
least discuss implementing that?
I'm a bit tired of troubleshooting branching-related package limbo
states twice a year :(
Fabio
10:17 a.m.
On Tue, Feb 08, 2022 at 04:30:30PM -0800, Kevin Fenzi wrote:
On Tue, Feb 08, 2022 at 03:53:51PM -0800, Michel Alexandre Salim
wrote:
> On Tue, Feb 08, 2022 at 09:28:53PM +0100, Tomas Hrcka wrote:
> > Hi All,
> >
> > Fedora 36 has now been branched, please be sure to do a git pull
> > --rebase to pick up the new branch, as an additional reminder
>
> Most of my packages appear to have f36 branches, but of the two new
> packages I just requested yesterday,
>
> - the_foundation has a f36 branch
> - lagrange doesn't
>
> Should I just request it manually?
Yep.
That seems to be failing right now:
https://pagure.io/releng/fedora-scm-requests/issue/41998
Invalid body, keys: sls missing
The problem is... the keys in the request are exactly the same as in
every other requests I see. Is f36 not set up properly yet for
request-branch?
Thanks,
--
Michel Alexandre Salim
identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2
11:12 a.m.
On Tue, 8 Feb 2022 at 20:40, Tomas Hrcka <thrcka(a)redhat.com> wrote:
Hi All,
Fedora 36 has now been branched, please be sure to do a git pull
--rebase to pick up the new branch, as an additional reminder
rawhide/f36 has been completely isolated from previous releases, so
What does this mean?
this means that anything you do for f36 you also have to do in the
rawhide branch and do a build there.
Right, f36 is a separate branch from rawhide now. That makes sense.
What does "rawhide/f36 has been completely isolated from previous
releases" mean? If it's trying to say "rawhide and f36 are now
separate branches" it fails to do so. Is it supposed to say
rawhide/f37?
11:26 a.m.
On Wed, Feb 9, 2022 at 6:12 PM Jonathan Wakely <jwakely(a)redhat.com> wrote:
On Tue, 8 Feb 2022 at 20:40, Tomas Hrcka <thrcka(a)redhat.com> wrote:
>
> Hi All,
>
> Fedora 36 has now been branched, please be sure to do a git pull
> --rebase to pick up the new branch, as an additional reminder
> rawhide/f36 has been completely isolated from previous releases, so
What does this mean?
> this means that anything you do for f36 you also have to do in the
> rawhide branch and do a build there.
Right, f36 is a separate branch from rawhide now. That makes sense.
What does "rawhide/f36 has been completely isolated from previous
releases" mean? If it's trying to say "rawhide and f36 are now
separate branches" it fails to do so. Is it supposed to say
rawhide/f37?
Yeah, that template sounds really archaic by todays standards, and
it's at least misleading or even wrong in some regards.
So it could benefit from being updateg ... Is it maintained in a
public repo somewhere where one could submit a PR to fix it? :)
Fabio
On Wed, Feb 9, 2022 at 6:12 PM Jonathan Wakely <jwakely(a)redhat.com> wrote:
On Tue, 8 Feb 2022 at 20:40, Tomas Hrcka <thrcka(a)redhat.com> wrote:
>
> Hi All,
>
> Fedora 36 has now been branched, please be sure to do a git pull
> --rebase to pick up the new branch, as an additional reminder
> rawhide/f36 has been completely isolated from previous releases, so
What does this mean?
> this means that anything you do for f36 you also have to do in the
> rawhide branch and do a build there.
Right, f36 is a separate branch from rawhide now. That makes sense.
What does "rawhide/f36 has been completely isolated from previous
releases" mean? If it's trying to say "rawhide and f36 are now
separate branches" it fails to do so. Is it supposed to say
rawhide/f37?
> _______________________________________________
> 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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
12:15 p.m.
On Wed, Feb 09, 2022 at 06:26:44PM +0100, Fabio Valentini wrote:
On Wed, Feb 9, 2022 at 6:12 PM Jonathan Wakely
<jwakely(a)redhat.com> wrote:
>
> On Tue, 8 Feb 2022 at 20:40, Tomas Hrcka <thrcka(a)redhat.com> wrote:
> >
> > Hi All,
> >
> > Fedora 36 has now been branched, please be sure to do a git pull
> > --rebase to pick up the new branch, as an additional reminder
> > rawhide/f36 has been completely isolated from previous releases, so
>
> What does this mean?
>
> > this means that anything you do for f36 you also have to do in the
> > rawhide branch and do a build there.
>
> Right, f36 is a separate branch from rawhide now. That makes sense.
> What does "rawhide/f36 has been completely isolated from previous
> releases" mean? If it's trying to say "rawhide and f36 are now
> separate branches" it fails to do so. Is it supposed to say
> rawhide/f37?
Yeah, that template sounds really archaic by todays standards, and
it's at least misleading or even wrong in some regards.
So it could benefit from being updateg ... Is it maintained in a
public repo somewhere where one could submit a PR to fix it? :)
Well, it means _builds_ are not inherited between them.
Long ago we used to let branched inherit into rawhide until there was a
branched build. This turned out to cause a number of problems so we
stopped doing it. So now if you do a f36 build, you need to also make
sure to do a f37 one as well.
I am pretty sure the wording here dates to around that time.
I would expect that text to be in
https://docs.pagure.org/releng/sop_mass_branching.html
but I guess it's not. I will ask...
kevin
12:20 p.m.
On Wed, Feb 09, 2022 at 09:39:16AM +0100, Fabio Valentini wrote:
On Wed, Feb 9, 2022 at 2:32 AM Kevin Fenzi <kevin(a)scrye.com>
wrote:
>
> And I suppose we should really look at disabling builds on mass branch
> day (while it's happening) it never ends well. :)
Should I open a FESCo / Releng / Infra ticket for this, so we can at
least discuss implementing that?
I'm a bit tired of troubleshooting branching-related package limbo
states twice a year :(
Sure. releng please.
The thing thats stopped us from doing this is figuring out a good way to
deny users ability to build, but yet let builders work and releng
processes work. I suppose we could just block external koji access, but
it would be a pretty unfriendly message and get a lot of 'is koji down'
messages. But perhaps we can come up with something.
kevin
3:12 p.m.
On Wed, Feb 09, 2022 at 05:12:16PM +0000, Jonathan Wakely wrote:
On Tue, 8 Feb 2022 at 20:40, Tomas Hrcka <thrcka(a)redhat.com>
wrote:
>
> Hi All,
>
> Fedora 36 has now been branched, please be sure to do a git pull
> --rebase to pick up the new branch
This part also doesn't make sense… You can do 'git fetch' to learn about
the new branch. There is nothing to pull (no new commits), and nothing
to rebase, since none of existing branches are affected.
Zbyszek
1:11 p.m.
On 09. 02. 22 22:12, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Feb 09, 2022 at 05:12:16PM +0000, Jonathan Wakely wrote:
> On Tue, 8 Feb 2022 at 20:40, Tomas Hrcka <thrcka(a)redhat.com> wrote:
>>
>> Hi All,
>>
>> Fedora 36 has now been branched, please be sure to do a git pull
>> --rebase to pick up the new branch
This part also doesn't make sense… You can do 'git fetch' to learn about
the new branch. There is nothing to pull (no new commits), and nothing
to rebase, since none of existing branches are affected.
As is said every 6 months on this list.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
9:30 a.m.
On Wed, 9 Feb 2022 at 18:15, Kevin Fenzi <kevin(a)scrye.com> wrote:
On Wed, Feb 09, 2022 at 06:26:44PM +0100, Fabio Valentini wrote:
> On Wed, Feb 9, 2022 at 6:12 PM Jonathan Wakely <jwakely(a)redhat.com> wrote:
> >
> > On Tue, 8 Feb 2022 at 20:40, Tomas Hrcka <thrcka(a)redhat.com> wrote:
> > >
> > > Hi All,
> > >
> > > Fedora 36 has now been branched, please be sure to do a git pull
> > > --rebase to pick up the new branch, as an additional reminder
> > > rawhide/f36 has been completely isolated from previous releases, so
> >
> > What does this mean?
> >
> > > this means that anything you do for f36 you also have to do in the
> > > rawhide branch and do a build there.
> >
> > Right, f36 is a separate branch from rawhide now. That makes sense.
> > What does "rawhide/f36 has been completely isolated from previous
> > releases" mean? If it's trying to say "rawhide and f36 are now
> > separate branches" it fails to do so. Is it supposed to say
> > rawhide/f37?
>
> Yeah, that template sounds really archaic by todays standards, and
> it's at least misleading or even wrong in some regards.
> So it could benefit from being updateg ... Is it maintained in a
> public repo somewhere where one could submit a PR to fix it? :)
Well, it means _builds_ are not inherited between them.
Long ago we used to let branched inherit into rawhide until there was a
branched build. This turned out to cause a number of problems so we
stopped doing it. So now if you do a f36 build, you need to also make
sure to do a f37 one as well.
I can't see how "rawhide/f36 has been completely isolated from
previous releases" can be interpreted to mean that :-)
f36 was already isolated from f35 and the other previous releases.
rawhide has now been isolated from f36 (which is not a release).
How about rewording it as:
"Fedora 36 has now been branched, please be sure to do a git fetch
to pick up the new branch. As f36 and rawhide are now separate branches,
anything you do for f36 must also be done in the rawhide branch."
(This seems backwards for my workflow. If I wanted to make a change on
both rawhide and f36 I'd do it in rawhide and do a fast-forward merge
to get it on the f36 branch, but this announcement probably isn't the
place to be giving people tips on git workflow.)
The next part seems OK ...
"There will be a Fedora 36 compose and it'll appear in
http://dl.fedoraproject.org/pub/fedora/linux/development/36/ once
complete. Please be sure to check it out."
Although I'd avoid the contraction "it'll" and I'm not sure what
"check it out" means. Is it telling me to checkout a Git branch?
Because that's how it could be interpreted. I think it's telling me to
try the 36 compose. "Please be sure" sounds like this is something I
*should* be doing as a package maintainer, but I'm afraid I never
routinely try pre-release composes. Maybe it should simply encourage
people to try it, not sound like it's compulsory.
12:12 p.m.
On Mon, Feb 14, 2022 at 03:30:52PM +0000, Jonathan Wakely wrote:
I can't see how "rawhide/f36 has been completely isolated from
previous releases" can be interpreted to mean that :-)
Well, long ago when we branched, there was a inheritence chain in koji,
so if you built something in F(n-1) it just got inherited into F(n).
So, ie, if you built foo-1.0-1.fc36 it would just also appear in rawhide
until you specifically did a rawhide build). This just caused a lot of
problems, and I think this announcement dates back to when that just
happened. So, now it's causing confusion the other way. :)
f36 was already isolated from f35 and the other previous releases.
rawhide has now been isolated from f36 (which is not a release).
How about rewording it as:
"Fedora 36 has now been branched, please be sure to do a git fetch
to pick up the new branch. As f36 and rawhide are now separate branches,
anything you do for f36 must also be done in the rawhide branch."
(This seems backwards for my workflow. If I wanted to make a change on
both rawhide and f36 I'd do it in rawhide and do a fast-forward merge
to get it on the f36 branch, but this announcement probably isn't the
place to be giving people tips on git workflow.)
The next part seems OK ...
"There will be a Fedora 36 compose and it'll appear in
http://dl.fedoraproject.org/pub/fedora/linux/development/36/ once
complete. Please be sure to check it out."
Although I'd avoid the contraction "it'll" and I'm not sure what
"check it out" means. Is it telling me to checkout a Git branch?
Because that's how it could be interpreted. I think it's telling me to
try the 36 compose. "Please be sure" sounds like this is something I
*should* be doing as a package maintainer, but I'm afraid I never
routinely try pre-release composes. Maybe it should simply encourage
people to try it, not sound like it's compulsory.
Yeah, I am going to get all these announcements checked into git and
adjusted. Thanks for the good feedback on it.
kevin
2:16 p.m.
On Mon, 14 Feb 2022 at 18:14, Kevin Fenzi <kevin(a)scrye.com> wrote:
On Mon, Feb 14, 2022 at 03:30:52PM +0000, Jonathan Wakely wrote:
>
> I can't see how "rawhide/f36 has been completely isolated from
> previous releases" can be interpreted to mean that :-)
Well, long ago when we branched, there was a inheritence chain in koji,
so if you built something in F(n-1) it just got inherited into F(n).
So, ie, if you built foo-1.0-1.fc36 it would just also appear in rawhide
until you specifically did a rawhide build). This just caused a lot of
problems, and I think this announcement dates back to when that just
happened. So, now it's causing confusion the other way. :)
My point is more that "rawhide/f36 has been isolated" makes no sense.
Note it's phrased as singular, as though "rawhide slash f36" is a
single thing. It's not, it's two branches now. Does it mean "rawhide
and f36 have been isolated"? Or "rawhide/f37"? The confusion is not
because of historical practice, it's because the words just don't make
any sense.
> f36 was already isolated from f35 and the other previous releases.
> rawhide has now been isolated from f36 (which is not a release).
>
> How about rewording it as:
>
> "Fedora 36 has now been branched, please be sure to do a git fetch
> to pick up the new branch. As f36 and rawhide are now separate branches,
> anything you do for f36 must also be done in the rawhide branch."
>
> (This seems backwards for my workflow. If I wanted to make a change on
> both rawhide and f36 I'd do it in rawhide and do a fast-forward merge
> to get it on the f36 branch, but this announcement probably isn't the
> place to be giving people tips on git workflow.)
>
> The next part seems OK ...
>
> "There will be a Fedora 36 compose and it'll appear in
> http://dl.fedoraproject.org/pub/fedora/linux/development/36/ once
> complete. Please be sure to check it out."
>
> Although I'd avoid the contraction "it'll" and I'm not sure
what
> "check it out" means. Is it telling me to checkout a Git branch?
> Because that's how it could be interpreted. I think it's telling me to
> try the 36 compose. "Please be sure" sounds like this is something I
> *should* be doing as a package maintainer, but I'm afraid I never
> routinely try pre-release composes. Maybe it should simply encourage
> people to try it, not sound like it's compulsory.
Yeah, I am going to get all these announcements checked into git and
adjusted. Thanks for the good feedback on it.
Great, thanks!
810
days inactive
816
days old
16 comments
9 participants
participants (9)
-
Adam Williamson -
Artur Frenszek-Iwicki -
Fabio Valentini -
Jonathan Wakely -
Kevin Fenzi -
Michel Alexandre Salim -
Miro Hrončok -
Tomas Hrcka -
Zbigniew Jędrzejewski-Szmek