11:44 a.m.
Hi All,
Fedora Linux 38 has now been branched, please be sure to do a git pull
--rebase to pick up the new branch, as an additional reminder
rawhide/f39 has been completely isolated from previous releases, so
this means that anything you do for f38 you also have to do in the
rawhide branch and do a build there. There will be a Fedora Linux 38 compose
and it'll appear in
http://dl.fedoraproject.org/pub/fedora/linux/development/38/ once
complete.
Bodhi is currently enabled in the f38 branch like it is for rawhide,
with automatic update creation. At the hit Beta change freeze point
in the Fedora Linux 38 schedule[1] updates-testing will be enabled and
manual bodhi updates will be required as in all stable releases.
Two things to remember:
1. The modules will be built for a new platform:f39
2. F38/branched release is frozen right now until we get a successful
compose, expect that your f38 builds won't be available immediately.
Thanks for understanding.
Tomas Hrcka
Fedora Release Engineering
[1] https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html
_______________________________________________
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, report it: https://pagure.io/fedora-infrastructure/new_issue
2:43 a.m.
Hello Tomas,
thank you for the announcement.
We also branched Fedora 38 in Copr so that everybody can submit builds
for it by now. Also, all projects with the "Follow Fedora branching"
option configured in their project settings have F38 chroots
automatically enabled and they contain the last build results from
Fedora Rawhide before the branch.
Jakub
On Thu, Feb 9, 2023 at 8:14 PM Tomas Hrcka <thrcka(a)redhat.com> wrote:
Hi All,
Fedora Linux 38 has now been branched, please be sure to do a git pull
--rebase to pick up the new branch, as an additional reminder
rawhide/f39 has been completely isolated from previous releases, so
this means that anything you do for f38 you also have to do in the
rawhide branch and do a build there. There will be a Fedora Linux 38 compose
and it'll appear in
http://dl.fedoraproject.org/pub/fedora/linux/development/38/ once
complete.
Bodhi is currently enabled in the f38 branch like it is for rawhide,
with automatic update creation. At the hit Beta change freeze point
in the Fedora Linux 38 schedule[1] updates-testing will be enabled and
manual bodhi updates will be required as in all stable releases.
Two things to remember:
1. The modules will be built for a new platform:f39
2. F38/branched release is frozen right now until we get a successful
compose, expect that your f38 builds won't be available immediately.
Thanks for understanding.
Tomas Hrcka
Fedora Release Engineering
[1] https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html
_______________________________________________
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, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
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, report it: https://pagure.io/fedora-infrastructure/new_issue
4:27 a.m.
On Fri, 10 Feb 2023 at 09:44, Jakub Kadlcik <jkadlcik(a)redhat.com> wrote:
Hello Tomas,
thank you for the announcement.
We also branched Fedora 38 in Copr so that everybody can submit builds
for it by now. Also, all projects with the "Follow Fedora branching"
option configured in their project settings have F38 chroots
automatically enabled and they contain the last build results from
Fedora Rawhide before the branch.
Is this still ongoing? I don't see F38 in my projects.
--
Iñaki Úcar
4:34 a.m.
On Fri, Feb 10, 2023 at 10:27 AM Iñaki Ucar <iucar(a)fedoraproject.org> wrote:
On Fri, 10 Feb 2023 at 09:44, Jakub Kadlcik <jkadlcik(a)redhat.com> wrote:
>
> Hello Tomas,
> thank you for the announcement.
>
> We also branched Fedora 38 in Copr so that everybody can submit builds
> for it by now. Also, all projects with the "Follow Fedora branching"
> option configured in their project settings have F38 chroots
> automatically enabled and they contain the last build results from
> Fedora Rawhide before the branch.
Is this still ongoing? I don't see F38 in my projects.
I do in all of my packages, you should just need to do a git pull to
get the new branches.
4:38 a.m.
On Fri, 10 Feb 2023 at 11:35, Peter Robinson <pbrobinson(a)gmail.com> wrote:
On Fri, Feb 10, 2023 at 10:27 AM Iñaki Ucar <iucar(a)fedoraproject.org> wrote:
>
> On Fri, 10 Feb 2023 at 09:44, Jakub Kadlcik <jkadlcik(a)redhat.com> wrote:
> >
> > Hello Tomas,
> > thank you for the announcement.
> >
> > We also branched Fedora 38 in Copr so that everybody can submit builds
> > for it by now. Also, all projects with the "Follow Fedora branching"
> > option configured in their project settings have F38 chroots
> > automatically enabled and they contain the last build results from
> > Fedora Rawhide before the branch.
>
> Is this still ongoing? I don't see F38 in my projects.
I do in all of my packages, you should just need to do a git pull to
get the new branches.
I meant in Copr.
--
Iñaki Úcar
3:46 a.m.
On pátek 10. února 2023 11:38:25 CET Iñaki Ucar wrote:
On Fri, 10 Feb 2023 at 11:35, Peter Robinson
<pbrobinson(a)gmail.com> wrote:
>
> On Fri, Feb 10, 2023 at 10:27 AM Iñaki Ucar <iucar(a)fedoraproject.org> wrote:
> >
> > On Fri, 10 Feb 2023 at 09:44, Jakub Kadlcik <jkadlcik(a)redhat.com> wrote:
> > >
> > > Hello Tomas,
> > > thank you for the announcement.
> > >
> > > We also branched Fedora 38 in Copr so that everybody can submit builds
> > > for it by now. Also, all projects with the "Follow Fedora
branching"
> > > option configured in their project settings have F38 chroots
> > > automatically enabled and they contain the last build results from
> > > Fedora Rawhide before the branch.
> >
> > Is this still ongoing? I don't see F38 in my projects.
>
> I do in all of my packages, you should just need to do a git pull to
> get the new branches.
I meant in Copr.
Just confirming - Copr branching is a two-phase process; we first link the
RPMs from rawhide to the branched release, and then we enable (when we know the
chroot is building fine).
https://docs.pagure.org/copr.copr/how_to_manage_chroots.html#branching-pr...
When Jakub announced, we just had those packages hardlinked, and RPMs available
on backend. But the 38 chroots got enabled later (next day).
Pavel
4:33 a.m.
On Tue, 14 Feb 2023 at 10:46, Pavel Raiskup <praiskup(a)redhat.com> wrote:
On pátek 10. února 2023 11:38:25 CET Iñaki Ucar wrote:
> On Fri, 10 Feb 2023 at 11:35, Peter Robinson <pbrobinson(a)gmail.com> wrote:
> >
> > On Fri, Feb 10, 2023 at 10:27 AM Iñaki Ucar <iucar(a)fedoraproject.org>
wrote:
> > >
> > > On Fri, 10 Feb 2023 at 09:44, Jakub Kadlcik <jkadlcik(a)redhat.com>
wrote:
> > > >
> > > > Hello Tomas,
> > > > thank you for the announcement.
> > > >
> > > > We also branched Fedora 38 in Copr so that everybody can submit
builds
> > > > for it by now. Also, all projects with the "Follow Fedora
branching"
> > > > option configured in their project settings have F38 chroots
> > > > automatically enabled and they contain the last build results from
> > > > Fedora Rawhide before the branch.
> > >
> > > Is this still ongoing? I don't see F38 in my projects.
> >
> > I do in all of my packages, you should just need to do a git pull to
> > get the new branches.
>
> I meant in Copr.
Just confirming - Copr branching is a two-phase process; we first link the
RPMs from rawhide to the branched release, and then we enable (when we know the
chroot is building fine).
https://docs.pagure.org/copr.copr/how_to_manage_chroots.html#branching-pr...
When Jakub announced, we just had those packages hardlinked, and RPMs available
on backend. But the 38 chroots got enabled later (next day).
Ok, got it, thanks.
--
Iñaki Úcar
8:48 a.m.
V Fri, Feb 10, 2023 at 11:15:25AM +0100, Petr Pisar napsal(a):
V Thu, Feb 09, 2023 at 06:44:03PM +0100, Tomas Hrcka napsal(a):
> Two things to remember:
>
> 1. The modules will be built for a new platform:f39
Thanks for thinking of modules. I've actually started the rebuild and slowly
going through the 46 streams.
I finished rebuilding the modules: 37 done, 11 failed, 1 skipped. I reported
all the build failures. For your information, here is the list (the #numbers
are MBS build identifiers):
Done:
avocado:latest #15978
cri-o:1.22 #15980
cri-o:1.23 #15981
cri-o:1.24 #15983
ghc:8.10 #15985
avocado-vt:latest - depends on avocado:latest #15986
mysql:8.0 #16042
nextcloud:nextcloud-stable #15988
nextcloud:23 #15990
nextcloud:24 #16044
nginx:mainline #16051
nginx:1.20 #16059
perl-bootstrap:5.34 #16065
perl-bootstrap:5.36 #16091
perl:5.34 - depends on perl-bootstrap:5.34, #16081
perl:5.36 - depends on perl-bootstrap:5.36 #16104
perl-App-cpanminus:1.7045 - depends on perl:5.34, perl:5.36, perl-YAML:1.30 #16205,
#16206
perl-Date-Manip:6.86 - depends on perl:5.34, perl:5.36 #16197, #16198
perl-DBD-MySQL:4.050 #16172, #16173
perl-DBD-Pg:3.15 - depends on postgresql:14 #16257, #16258
perl-DBD-SQLite:1.70 #16180, #16181
perl-DBI:1.643 #16132, #16133
perl-IO-Socket-SSL:2.074 - depends on perl:5.34, perl:5.36 #16147, #16148
perl-IO-stringy:2.113 #16155, #16156
perl-libwww-perl:6.62 - depends on perl:5.34, perl:5.36, perl-IO-Socket-SSL:2.074 #16222,
#16223
perl-libwww-perl:6.67 - depends on perl:5.34, perl:5.36, perl-IO-Socket-SSL:2.074 #16214,
#16215
perl-YAML:1.30 - depends on perl:5.34, perl:5.36, perl-YAML-bootstrap:1.30 #16164, #16165
perl-YAML-bootstrap:1.30 - depends on perl:5.34, perl:5.36 #16124, #16125
postgresql:12 #16134
postgresql:13 #16016
postgresql:14 #16247 https://bugzilla.redhat.com/show_bug.cgi?id=2170745
postgresql:15 #16140
ruby:3.1 #16076
sway:rolling #16031
swig:4.0 #16085
swig:4.1 #16108
varnish:6.0 #16117
Skipped:
avocado-vt:82lts - depends on avocado:82lts
Failed:
avocado:82lts #15979, python-avocado-82.2-1 RPM build hangs
https://bugzilla.redhat.com/show_bug.cgi?id=2183989
cri-o:1.25 #15984 https://bugzilla.redhat.com/show_bug.cgi?id=2168860
mariadb:10.5 #15987 https://bugzilla.redhat.com/show_bug.cgi?id=2169678
mariadb:10.6 #16041 https://bugzilla.redhat.com/show_bug.cgi?id=2169678
mariadb:10.7 #16054 https://bugzilla.redhat.com/show_bug.cgi?id=2169678
mariadb:10.8 #16066 https://bugzilla.redhat.com/show_bug.cgi?id=2169678
mariadb:10.9 #16075 https://bugzilla.redhat.com/show_bug.cgi?id=2169678
nodejs:16 #16060 https://bugzilla.redhat.com/show_bug.cgi?id=2119713
perl-CGI:4.54 - depends on perl:5.34, perl:5.36, perl-libwww-perl:6.67, MBS times out on a
submission https://pagure.io/fm-orchestrator/issue/1759
perl-XML-Parser:2.46 - depends on perl:5.36, perl-libwww-perl:6.67, MBS times out on a
submission https://pagure.io/fm-orchestrator/issue/1759
subversion:1.14 - depends on swig:4.0 #16113, subversion RPM tests fail
https://bugzilla.redhat.com/show_bug.cgi?id=2170754
-- Petr
9:21 a.m.
On Thu, Feb 09, 2023 at 06:44:03PM +0100, Tomas Hrcka wrote:
Hi All,
Fedora Linux 38 has now been branched, please be sure to do a git pull
--rebase to pick up the new branch
I know this has been discussed seemingly on every branching since the
switch to git, but anyway...
'git pull --rebase' is a strange command to suggest. I does the job,
but almost by accident, and it's confusing things by mixing in rebasing.
Can we make this just say 'git fetch' or 'git fetch -v' ?
Zbyszek
11:55 a.m.
On Fri, Feb 10, 2023 at 03:21:06PM +0000, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Feb 09, 2023 at 06:44:03PM +0100, Tomas Hrcka wrote:
> Hi All,
>
> Fedora Linux 38 has now been branched, please be sure to do a git pull
> --rebase to pick up the new branch
I know this has been discussed seemingly on every branching since the
switch to git, but anyway...
'git pull --rebase' is a strange command to suggest. I does the job,
but almost by accident, and it's confusing things by mixing in rebasing.
Can we make this just say 'git fetch' or 'git fetch -v' ?
Sure!
I've pressed to move all our email announcements into git...
so https://pagure.io/releng/blob/main/f/mail-templates/03-mass-branch.txt
PR's welcome!
I mostly just moved the old email versions into there, so they could
likely use a lot of improvement.
kevin
12:08 p.m.
On Fri, Feb 10, 2023 at 09:55:47AM -0800, Kevin Fenzi wrote:
On Fri, Feb 10, 2023 at 03:21:06PM +0000, Zbigniew Jędrzejewski-Szmek
wrote:
> On Thu, Feb 09, 2023 at 06:44:03PM +0100, Tomas Hrcka wrote:
> > Hi All,
> >
> > Fedora Linux 38 has now been branched, please be sure to do a git pull
> > --rebase to pick up the new branch
>
> I know this has been discussed seemingly on every branching since the
> switch to git, but anyway...
>
> 'git pull --rebase' is a strange command to suggest. I does the job,
> but almost by accident, and it's confusing things by mixing in rebasing.
> Can we make this just say 'git fetch' or 'git fetch -v' ?
Sure!
I've pressed to move all our email announcements into git...
so https://pagure.io/releng/blob/main/f/mail-templates/03-mass-branch.txt
https://pagure.io/releng/pull-request/11272
Zbyszek
11:46 a.m.
Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Feb 09, 2023 at 06:44:03PM +0100, Tomas Hrcka wrote:
> Hi All,
>
> Fedora Linux 38 has now been branched, please be sure to do a git pull
> --rebase to pick up the new branch
I know this has been discussed seemingly on every branching since the
switch to git, but anyway...
'git pull --rebase' is a strange command to suggest. I does the job,
but almost by accident, and it's confusing things by mixing in rebasing.
Can we make this just say 'git fetch' or 'git fetch -v' ?
The thing is, you should ALWAYS git pull --rebase to pull from git
repositories, NEVER just git pull. Because:
1. it avoids those pesky merge commits, producing a nice linear history, and
2. (not relevant for Fedora dist-git, but for repositories that allow force
pushes) it also works if the repository has been force-pushed to.
See also (not by me):
https://coderwall.com/p/7aymfa/please-oh-please-use-git-pull-rebase
Kevin Kofler
12:20 p.m.
Kevin Kofler via devel wrote:
Zbigniew Jędrzejewski-Szmek wrote:
> 'git pull --rebase' is a strange command to suggest. I does the job,
> but almost by accident, and it's confusing things by mixing in rebasing.
> Can we make this just say 'git fetch' or 'git fetch -v' ?
The thing is, you should ALWAYS git pull --rebase to pull from git
repositories, NEVER just git pull.
While that was generally good advice (for folks who aren't
maintainers of an upstream project, i.e. most people), it's
not as accurate a statement as it once was.
Since git-2.33.1 (2021-10-12), `git pull` should not create
a merge commit by default. The default is --ff-only, which
means:
Only update to the new history if there is no divergent local
history. This is the default when no method for reconciling
divergent histories is provided (via the --rebase=* flags).
Running `git pull` should do what most people want without
the risk of surprising newer users due to a rebase with
conflicts. It's better to have the pull simply stop rather
than creating a merge (as it used to do) or attempting to
rebase automatically -- as a default.
Regardless, `git fetch` is the better recommendation here.
It achieves the goal of getting the newly-branched release
into the local repository and has no other effects.
--
Todd
395
days inactive
451
days old
13 comments
10 participants
participants (10)
-
Iñaki Ucar -
Jakub Kadlcik -
Kevin Fenzi -
Kevin Kofler -
Pavel Raiskup -
Peter Robinson -
Petr Pisar -
Todd Zullinger -
Tomas Hrcka -
Zbigniew Jędrzejewski-Szmek