Re: 01/01: gnu: mesa: Update to 18.2.3.

Re: 01/01: gnu: mesa: Update to 18.2.3.

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

Hello Rutger,

rhelling@mykolab.com (Rutger Helling) writes:

> rhelling pushed a commit to branch staging
> in repository guix.
>
> commit 77ec9b983087900d85b8de704902ff2c1afcb6c0
> Author: Rutger Helling <rhelling@mykolab.com>
> Date:   Fri Oct 19 18:35:50 2018 +0200
>
>     gnu: mesa: Update to 18.2.3.
>     
>     * gnu/packages/gl.scm (mesa): Update to 18.2.3.
> ---
>  gnu/packages/gl.scm | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gnu/packages/gl.scm b/gnu/packages/gl.scm
> index c005a6f..0c64e05 100644
> --- a/gnu/packages/gl.scm
> +++ b/gnu/packages/gl.scm
> @@ -224,7 +224,7 @@ also known as DXTn or DXTC) for Mesa.")
>  (define-public mesa
>    (package
>      (name "mesa")
> -    (version "18.2.2")
> +    (version "18.2.3")
>      (source
>        (origin
>          (method url-fetch)
> @@ -236,7 +236,7 @@ also known as DXTn or DXTC) for Mesa.")
>                                    version "/mesa-" version ".tar.xz")))
>          (sha256
>           (base32
> -          "1i3ky3d210vi3f5hlr9la1kspdyv093npndxsbzdklw95aqq5fn3"))
> +          "00rrg8i1ykwvrg94gcsvjy1l9ih8bqafkq9x122h3rkk5cvmnjcz"))

This hash does not correspond to the released tarball.  Can you
look into it?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: 01/01: gnu: mesa: Update to 18.2.3.

[Rutger Helling]

[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]

Hi Marius,

That's odd, I'm not sure what happened. I guess the hash must've
changed again after I pushed it (the release was on the same day). I've
updated to the latest stable version instead (18.2.6).

On Mon, 03 Dec 2018 20:34:57 +0100
Marius Bakke <mbakke@fastmail.com> wrote:

> Hello Rutger,
> 
> rhelling@mykolab.com (Rutger Helling) writes:
> 
> > rhelling pushed a commit to branch staging
> > in repository guix.
> >
> > commit 77ec9b983087900d85b8de704902ff2c1afcb6c0
> > Author: Rutger Helling <rhelling@mykolab.com>
> > Date:   Fri Oct 19 18:35:50 2018 +0200
> >
> >     gnu: mesa: Update to 18.2.3.
> >     
> >     * gnu/packages/gl.scm (mesa): Update to 18.2.3.
> > ---
> >  gnu/packages/gl.scm | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/gnu/packages/gl.scm b/gnu/packages/gl.scm
> > index c005a6f..0c64e05 100644
> > --- a/gnu/packages/gl.scm
> > +++ b/gnu/packages/gl.scm
> > @@ -224,7 +224,7 @@ also known as DXTn or DXTC) for Mesa.")
> >  (define-public mesa
> >    (package
> >      (name "mesa")
> > -    (version "18.2.2")
> > +    (version "18.2.3")
> >      (source
> >        (origin
> >          (method url-fetch)
> > @@ -236,7 +236,7 @@ also known as DXTn or DXTC) for Mesa.")
> >                                    version "/mesa-" version
> > ".tar.xz"))) (sha256
> >           (base32
> > -          "1i3ky3d210vi3f5hlr9la1kspdyv093npndxsbzdklw95aqq5fn3"))
> > +          "00rrg8i1ykwvrg94gcsvjy1l9ih8bqafkq9x122h3rkk5cvmnjcz"))
> 
> This hash does not correspond to the released tarball.  Can you
> look into it?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Starting the staging branch (was: Re: 01/01: gnu: mesa: Update to 18.2.3.)

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 386 bytes --]

Rutger Helling <rhelling@mykolab.com> writes:

> Hi Marius,
>
> That's odd, I'm not sure what happened. I guess the hash must've
> changed again after I pushed it (the release was on the same day). I've
> updated to the latest stable version instead (18.2.6).

OK, thank you!

Let's try to start building this branch soon.  I suppose we should wait
for the GNOME upgrade, Ricardo WDYT?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: Starting the staging branch (was: Re: 01/01: gnu: mesa: Update to 18.2.3.)

[Ricardo Wurmus]

Hi Marius,

> Rutger Helling <rhelling@mykolab.com> writes:
>
>> Hi Marius,
>>
>> That's odd, I'm not sure what happened. I guess the hash must've
>> changed again after I pushed it (the release was on the same day). I've
>> updated to the latest stable version instead (18.2.6).
>
> OK, thank you!
>
> Let's try to start building this branch soon.  I suppose we should wait
> for the GNOME upgrade, Ricardo WDYT?

I just pushed a new version of wip-gnome-upgrades, which appears to be
mostly fine.  (This is GNOME 3.28; I’m working on 3.30, which is
comparatively easy but requires more fundamental packages to be changed,
such as glib.)

I’m using GNOME 3.28 right now after changing my ~/.xsession file to end
like this:

--8<---------------cut here---------------start------------->8---
export GDK_BACKEND=x11
export DISPLAY=:0.0
gnome-session
--8<---------------cut here---------------end--------------->8---

(Previously it was just “gnome-session”.)

The default backend appears to be “wayland”, but I can’t seem to start
the sesson when xorg-server is running.  I also don’t understand why I
have to set DISPLAY; I think that this indicates that elogind doesn’t
consider my account to be logged in or something.

I also found that adjusting the brightness triggers an authentication
dialogue, asking me to input a password for gsd-backlight-helper.  This
looks like the same problem above.  Something with elogind seat
management, I guess.

If you understand this better please give it a try.

--
Ricardo