Shall we merge wip-gnome3.30 to core-updates?

Shall we merge wip-gnome3.30 to core-updates?

[Kei Kebreau]

Hi Marius,

Would it be okay to merge the wip-gnome3.30 branch into core-updates
after I do some local testing? I'd like to help out with updating GNOME
to 3.32, and I'm told that this is the first step towards that goal.

Thanks,
Kei

Re: Shall we merge wip-gnome3.30 to core-updates?

[Marius Bakke]

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

Hi Kei,

Kei Kebreau <kkebreau@posteo.net> writes:

> Hi Marius,
>
> Would it be okay to merge the wip-gnome3.30 branch into core-updates
> after I do some local testing? I'd like to help out with updating GNOME
> to 3.32, and I'm told that this is the first step towards that goal.

That sounds great, thanks :-)

I suggest we 'freeze' core-updates next weekend and start working on
merging it.  It has been sitting idle for way too long already!

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

Re: Shall we merge wip-gnome3.30 to core-updates?

[Ludovic Courtès]

Marius Bakke <mbakke@fastmail.com> skribis:

> Kei Kebreau <kkebreau@posteo.net> writes:
>
>> Hi Marius,
>>
>> Would it be okay to merge the wip-gnome3.30 branch into core-updates
>> after I do some local testing? I'd like to help out with updating GNOME
>> to 3.32, and I'm told that this is the first step towards that goal.
>
> That sounds great, thanks :-)
>
> I suggest we 'freeze' core-updates next weekend and start working on
> merging it.  It has been sitting idle for way too long already!

+1!

Ludo'.

Re: Shall we merge wip-gnome3.30 to core-updates?

[Kei Kebreau]

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

Hello again Marius,

Marius Bakke <mbakke@fastmail.com> writes:

> Hi Kei,
>
> Kei Kebreau <kkebreau@posteo.net> writes:
>
>> Hi Marius,
>>
>> Would it be okay to merge the wip-gnome3.30 branch into core-updates
>> after I do some local testing? I'd like to help out with updating GNOME
>> to 3.32, and I'm told that this is the first step towards that goal.
>
> That sounds great, thanks :-)
>
> I suggest we 'freeze' core-updates next weekend and start working on
> merging it.  It has been sitting idle for way too long already!

Some very brief updates:

* I've updated (on my own computer) the perl-net-ssleay package because
tests would freeze indefinitely due to a zombified perl process.

* I've also updated the perl-io-socket-ssl-openssl package because of a
plethora of test failures.

* The samba package seems to require the "rpcgen" binary as part of its
build process, but I don't know which package includes that binary. I
know it appears somewhere in the process of building the "gcc-toolchain"
package, but I'd rather not include that whole package if it isn't
necessary.

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

Re: Shall we merge wip-gnome3.30 to core-updates?

[Efraim Flashner]

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

On Thu, Jun 13, 2019 at 07:09:47PM -0400, Kei Kebreau wrote:
> Hello again Marius,
> 
> Marius Bakke <mbakke@fastmail.com> writes:
> 
> > Hi Kei,
> >
> > Kei Kebreau <kkebreau@posteo.net> writes:
> >
<...>
> 
> * The samba package seems to require the "rpcgen" binary as part of its
> build process, but I don't know which package includes that binary. I
> know it appears somewhere in the process of building the "gcc-toolchain"
> package, but I'd rather not include that whole package if it isn't
> necessary.


rpcgen seems to be in glibc


-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

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

Re: Shall we merge wip-gnome3.30 to core-updates?

[Marius Bakke]

[-- Attachment #1.1: Type: text/plain, Size: 843 bytes --]

Efraim Flashner <efraim@flashner.co.il> writes:

> On Thu, Jun 13, 2019 at 07:09:47PM -0400, Kei Kebreau wrote:
>> Hello again Marius,
>> 
>> Marius Bakke <mbakke@fastmail.com> writes:
>> 
>> > Hi Kei,
>> >
>> > Kei Kebreau <kkebreau@posteo.net> writes:
>> >
> <...>
>> 
>> * The samba package seems to require the "rpcgen" binary as part of its
>> build process, but I don't know which package includes that binary. I
>> know it appears somewhere in the process of building the "gcc-toolchain"
>> package, but I'd rather not include that whole package if it isn't
>> necessary.
>
>
> rpcgen seems to be in glibc

Not since commit 3670ea70e2e932969a3ffc0acf75a714c7b42540 ;-)

This patch allows Samba to build.  Other distributions seem to give
Samba libtirpc as input too, so I haven't finished investigating yet:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: samba.patch --]
[-- Type: text/x-patch, Size: 2866 bytes --]

From 9be0787b1b2a55aecefaba09dc73836c1931e10a Mon Sep 17 00:00:00 2001
From: Marius Bakke <mbakke@fastmail.com>
Date: Sun, 16 Jun 2019 08:21:11 +0200
Subject: [PATCH 1/2] gnu: Add rpcsvc-proto.

* gnu/packages/onc-rpc.scm (rpcsvc-proto): New public variable.
---
 gnu/packages/onc-rpc.scm | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/gnu/packages/onc-rpc.scm b/gnu/packages/onc-rpc.scm
index 64887212d3..f3ce12ef7a 100644
--- a/gnu/packages/onc-rpc.scm
+++ b/gnu/packages/onc-rpc.scm
@@ -99,6 +99,26 @@ IPv4 and IPv6.  ONC RPC is notably used by the network file system (NFS).")
 universal addresses.")
     (license bsd-3)))
 
+(define-public rpcsvc-proto
+  (package
+    (name "rpcsvc-proto")
+    (version "1.4")
+    (home-page "https://github.com/thkukuk/rpcsvc-proto")
+    (source (origin
+              (method url-fetch)
+              (uri (string-append home-page "/releases/download/v" version
+                                  "/rpcsvc-proto-" version ".tar.xz"))
+              (sha256
+               (base32
+                "0i93wbpw5dk2gf5v4a5hq6frh814wzgjydh7saj28wlgbpqdaja1"))))
+    (build-system gnu-build-system)
+    (synopsis "RPCSVC protocol definitions")
+    (description
+     "This package provides @code{rpcsvc} @file{protocol.x} files and headers
+that are not included with the @code{libtirpc} package.  Additionally it
+contains @command{rpcgen}, which is used to produce header files and sources
+from the protocol files.")
+    (license bsd-3)))
 
 (define-public libnsl
   (package
-- 
2.22.0


From bb49cb2307bcfb4274af1b80498ac8625a2891b8 Mon Sep 17 00:00:00 2001
From: Marius Bakke <mbakke@fastmail.com>
Date: Sun, 16 Jun 2019 08:21:57 +0200
Subject: [PATCH 2/2] gnu: samba: Add rpcgen input.

This is required because Glibc no longer provides this executable since
commit 3670ea70e2e932969a3ffc0acf75a714c7b42540.

* gnu/packages/samba.scm (samba)[native-inputs]: Add RPCSVC-PROTO.
---
 gnu/packages/samba.scm | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gnu/packages/samba.scm b/gnu/packages/samba.scm
index 7803a1c8d1..c4a40187c4 100644
--- a/gnu/packages/samba.scm
+++ b/gnu/packages/samba.scm
@@ -43,6 +43,7 @@
   #:use-module (gnu packages gnupg)
   #:use-module (gnu packages kerberos)
   #:use-module (gnu packages linux)
+  #:use-module (gnu packages onc-rpc)
   #:use-module (gnu packages openldap)
   #:use-module (gnu packages perl)
   #:use-module (gnu packages pkg-config)
@@ -225,6 +226,7 @@ anywhere.")
     (native-inputs
      `(("docbook-xsl" ,docbook-xsl)    ;for generating manpages
        ("xsltproc" ,libxslt)           ;ditto
+       ("rpcsvc-proto" ,rpcsvc-proto)  ;for 'rpcgen'
        ("perl" ,perl)
        ("pkg-config" ,pkg-config)
        ("python" ,python)))
-- 
2.22.0


[-- Attachment #1.3: Type: text/plain, Size: 125 bytes --]


@Kei: If you have tested this branch elsewhere, I think it's okay to
merge even if it does not yet build on 'core-updates'.

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

'core-updates' summer 2019

[Marius Bakke]

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

Ludovic Courtès <ludo@gnu.org> writes:

> Marius Bakke <mbakke@fastmail.com> skribis:
>
>> I suggest we 'freeze' core-updates next weekend and start working on
>> merging it.  It has been sitting idle for way too long already!
>
> +1!

The weekend is here already!  But we are still missing glibc 2.29, so I
suggest we postpone the freeze a bit.  There are also many TODOs and
XXXs that mention rebuild cycles, now is the time to fix those!

We should also update linux-libre-headers to the latest LTS while at it.
Anything else?

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

Re: Shall we merge wip-gnome3.30 to core-updates?

[Kei Kebreau]

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

Marius Bakke <mbakke@fastmail.com> writes:

> Efraim Flashner <efraim@flashner.co.il> writes:
>
>> On Thu, Jun 13, 2019 at 07:09:47PM -0400, Kei Kebreau wrote:
>>> Hello again Marius,
>>> 
>>> Marius Bakke <mbakke@fastmail.com> writes:
>>> 
>>> > Hi Kei,
>>> >
>>> > Kei Kebreau <kkebreau@posteo.net> writes:
>>> >
>> <...>
>>> 
>>> * The samba package seems to require the "rpcgen" binary as part of its
>>> build process, but I don't know which package includes that binary. I
>>> know it appears somewhere in the process of building the "gcc-toolchain"
>>> package, but I'd rather not include that whole package if it isn't
>>> necessary.
>>
>>
>> rpcgen seems to be in glibc

I saw that too, but running "guix build glibc" gives a glibc without the
"rpcgen" binary.

>
> Not since commit 3670ea70e2e932969a3ffc0acf75a714c7b42540 ;-)

Aha!

>
> This patch allows Samba to build.  Other distributions seem to give
> Samba libtirpc as input too, so I haven't finished investigating yet:
>
...
> @Kei: If you have tested this branch elsewhere, I think it's okay to
> merge even if it does not yet build on 'core-updates'.

Great! I'll give the branch a test on top of "master" first.

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

Re: 'core-updates' summer 2019

[Mark H Weaver]

Marius Bakke <mbakke@fastmail.com> writes:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Marius Bakke <mbakke@fastmail.com> skribis:
>>
>>> I suggest we 'freeze' core-updates next weekend and start working on
>>> merging it.  It has been sitting idle for way too long already!
>>
>> +1!
>
> The weekend is here already!  But we are still missing glibc 2.29, so I
> suggest we postpone the freeze a bit.  There are also many TODOs and
> XXXs that mention rebuild cycles, now is the time to fix those!
>
> We should also update linux-libre-headers to the latest LTS while at it.
> Anything else?

I noticed several months ago that the new commencement packages
introduce many phases that return values other than #t.  It would be
nice to fix those.

      Mark

Re: 'core-updates' summer 2019

[Ludovic Courtès]

Hi,

Marius Bakke <mbakke@fastmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Marius Bakke <mbakke@fastmail.com> skribis:
>>
>>> I suggest we 'freeze' core-updates next weekend and start working on
>>> merging it.  It has been sitting idle for way too long already!
>>
>> +1!
>
> The weekend is here already!  But we are still missing glibc 2.29, so I
> suggest we postpone the freeze a bit.

Should we?  Attached is my current WIP for glibc 2.29, where Python now
fails to build with:

--8<---------------cut here---------------start------------->8---
LD_LIBRARY_PATH=/tmp/guix-build-python-minimal-3.7.3.drv-0/Python-3.7.3 CC='gcc -pthread' LDSHARED='gcc -pthread -shared -Wl,-rpath=/gnu/store/wxw0wbizbaiha0bisrqsdzg1ggf7kndc-python-minimal-3.7.3/lib   ' OPT='-DNDEBUG -g -fwrapv -O3 -Wall' 	_TCLTK_INCLUDES='' _TCLTK_LIBS='' 	./python -E ./setup.py  build

[...]

libgcc_s.so.1 must be installed for pthread_cancel to work
libgcc_s.so.1 must be installed for pthread_cancel to work
libgcc_s.so.1 must be installed for pthread_cancel to work
/gnu/store/r28awwz5vvkn5fqfv8nww6wkxis1d1vs-bootstrap-binaries-0/bin/sh: line 9:  9025 Aborted                 LD_LIBRARY_PATH=/tmp/guix-build-python-minimal-3.7.3.drv-0/Python-3.7.3 CC='gcc -pthread' LDSHARED='gcc -pthread -shared -Wl,-rpath=/gnu/store/wxw0wbizbaiha0bisrqsdzg1ggf7kndc-python-minimal-3.7.3/lib   ' OPT='-DNDEBUG -g -fwrapv -O3 -Wall' _TCLTK_INCLUDES='' _TCLTK_LIBS='' ./python -E ./setup.py $quiet build
make: *** [Makefile:626: sharedmods] Error 134
--8<---------------cut here---------------end--------------->8---

It looks like libgcc_s.so is not in the RUNPATH of ‘python’.  We
explicitly fix it in ‘gcc’ but here it’s:

      ("gcc-wrapper" . "/gnu/store/nidn7vgqr488iwmar9wan1gg8y6c399j-gcc-mesboot-wrapper-4.7.4")
      ("gcc" . "/gnu/store/7fpm7qm8n4wa7frgv13j9jrbcpwrxr99-gcc-mesboot-4.9.4")

and I’m not sure how to fix it.

(It’s surprising there are two distinct versions here.)

> There are also many TODOs and XXXs that mention rebuild cycles, now is
> the time to fix those!

Indeed!  I’ll take a look.

Thanks,
Ludo’.

Re: Shall we merge wip-gnome3.30 to core-updates?

[Kei Kebreau]

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

Kei Kebreau <kkebreau@posteo.net> writes:

> Marius Bakke <mbakke@fastmail.com> writes:
>
>> @Kei: If you have tested this branch elsewhere, I think it's okay to
>> merge even if it does not yet build on 'core-updates'.
>
> Great! I'll give the branch a test on top of "master" first.

Update on the GNOME updates: while most things seem to be working as they
were before, others may be off in subtle ways. For example, the time
display is UTC and seemingly unchangeable.

This could be partly caused by the fact that only some of the GNOME
packages were updated to their 3.30 versions, but I don't know how GNOME
works well enough to diagnose the issue right away.

If this is okay, I can push the updates tomorrow.

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

Re: Shall we merge wip-gnome3.30 to core-updates?

[Ricardo Wurmus]

Hi Kei,

> This could be partly caused by the fact that only some of the GNOME
> packages were updated to their 3.30 versions, but I don't know how GNOME
> works well enough to diagnose the issue right away.

What GNOME packages that should be updated haven’t been updated ?

> If this is okay, I can push the updates tomorrow.

That’s fine.  Then we’ll have to add the missing updates in the days
after that.

--
Ricardo

Re: Shall we merge wip-gnome3.30 to core-updates?

[Kei Kebreau]

Ricardo Wurmus <rekado@elephly.net> writes:

> Hi Kei,
>
>> This could be partly caused by the fact that only some of the GNOME
>> packages were updated to their 3.30 versions, but I don't know how GNOME
>> works well enough to diagnose the issue right away.
>
> What GNOME packages that should be updated haven’t been updated ?
>
>> If this is okay, I can push the updates tomorrow.
>
> That’s fine.  Then we’ll have to add the missing updates in the days
> after that.
>
> --
> Ricardo

Alright! I've pushed the existing GNOME updates to core-updates.

Below is a list of GNOME packages that are propagated in the "gnome"
package definition that aren't at their highest 3.30 bug fix
number or aren't updated to version 3.30 (or for differently-versioned
packages, their latest stable version from what I can tell at a glance):

baobab (gnome.scm)
font-cantarell (fonts.scm)
epiphany (gnome.scm)
file-roller (gnome.scm)
gedit (gnome.scm)
glib-networking (gnome.scm)
gnome-backgrounds (gnome.scm)
gnome-calculator (gnome.scm)
gnome-control-center (gnome.scm)
gnome-online-accounts (gnome.scm)
gnome-session (gnome.scm)
gnome-settings-daemon (gnome.scm)
gnome-terminal (gnome.scm)
gucharmap (gnome.scm)
gvfs (gnome.scm)
nautilus (gnome.scm)
shared-mime-info (gnome.scm)
totem (gnome.scm)
zenity (gnome.scm)

Perhaps there's something there (mismatch between gnome-shell and
gnome-control-center?) that affects the clock.