On Mon, 14 Feb 2022 at 18:14, Kevin Fenzi wrote:
>
> On Mon, Feb 14, 2022 at 03:30:52PM +, 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
On Mon, Feb 14, 2022 at 03:30:52PM +, 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)
On Wed, 9 Feb 2022 at 18:15, Kevin Fenzi 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 wrote:
> > >
> > > On Tue, 8 Feb 2022 at 20:40, Tomas Hrcka wrote:
> > > >
> > > > Hi All,
> > > >
> > > > Fedora 36 has now
On 09. 02. 22 22:12, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Feb 09, 2022 at 05:12:16PM +, Jonathan Wakely wrote:
On Tue, 8 Feb 2022 at 20:40, 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
This part
On Wed, Feb 09, 2022 at 05:12:16PM +, Jonathan Wakely wrote:
> On Tue, 8 Feb 2022 at 20:40, 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
This part also doesn't make sense… You can do 'git
On Wed, Feb 09, 2022 at 09:39:16AM +0100, Fabio Valentini wrote:
> On Wed, Feb 9, 2022 at 2:32 AM Kevin Fenzi 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
On Wed, Feb 09, 2022 at 06:26:44PM +0100, Fabio Valentini wrote:
> On Wed, Feb 9, 2022 at 6:12 PM Jonathan Wakely wrote:
> >
> > On Tue, 8 Feb 2022 at 20:40, Tomas Hrcka wrote:
> > >
> > > Hi All,
> > >
> > > Fedora 36 has now been branched, please be sure to do a git pull
> > > --rebase to pick
On Wed, Feb 9, 2022 at 6:12 PM Jonathan Wakely wrote:
>
> On Tue, 8 Feb 2022 at 20:40, 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
> > rawhide/f36 has been completely
On Tue, 8 Feb 2022 at 20:40, 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
> rawhide/f36 has been completely isolated from previous releases, so
What does this mean?
> this
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
> > >
On Wed, Feb 9, 2022 at 2:32 AM Kevin Fenzi 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
On Wed, Feb 09, 2022 at 12:42:25AM -, 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
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
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
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
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
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
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
18 matches
Mail list logo
