On Tue, 2018-03-06 at 12:57 +, Leigh Scott wrote:
> > On Mon, 2018-03-05 at 18:03 +0100, Kalev Lember wrote:
> >
> > Much as I would like to, the change process does exist, and says it's
> > far too late for that for F28 gold.
>
> Can't new Xorg wait till F29?, isn't this change to big and
> On Mon, 2018-03-05 at 18:03 +0100, Kalev Lember wrote:
>
> Much as I would like to, the change process does exist, and says it's
> far too late for that for F28 gold.
>
> - ajax
Can't new Xorg wait till F29?, isn't this change to big and prone to breakage
to be pushed after F28 release?
On Mon, 2018-03-05 at 18:03 +0100, Kalev Lember wrote:
> On 03/05/2018 05:48 PM, Adam Jackson wrote:
> > Short version:
> >
> > $ sudo dnf copr enable ajax/upstream
> > $ sudo dnf upgrade
> >
> > Long version:
> >
> > I've set up a copr containing a rebuild of the X server and drivers for
> > th
>
>
> I would say the opposite: land this today so that it can get in F28 Beta
> (tomorrow starts package freeze for the beta release), and don't do a
> post release update that changes the drivers ABI.
>
>
This should have happened via the System Wide Changes proces, isn´t? At
less a Freeze except
On 03/05/2018 05:48 PM, Adam Jackson wrote:
> Short version:
>
> $ sudo dnf copr enable ajax/upstream
> $ sudo dnf upgrade
>
> Long version:
>
> I've set up a copr containing a rebuild of the X server and drivers for
> the upstream 1.20 release candidates. Unfortunately the upstream and
> Fedora
Short version:
$ sudo dnf copr enable ajax/upstream
$ sudo dnf upgrade
Long version:
I've set up a copr containing a rebuild of the X server and drivers for
the upstream 1.20 release candidates. Unfortunately the upstream and
Fedora schedules didn't line up as well as I'd have liked, so I'm not
