Re: installer no longer signals success or offer reboot

2020-06-14 Thread Mathieu Othacehe


> I feel a bit stuck here, I cannot find an alternative to overlayfs and
> on the other hand umounting the overlay is problematic.
>
> Do people have some ideas here?

Ok, this should be fixed with: 876a8d987085b8c64f32c8a320e4219575af285c.

Thanks,

Mathieu



Checking for profile collisions with ‘guix lint’

2020-06-14 Thread Ludovic Courtès
Hello,

Ludovic Courtès  skribis:

> Edouard Klein  skribis:
>
>> Because of the subtle consequences of editing a package are hard to keep
>> track of, I wrote the attached script (you need sharness to run it, but
>> with slight modification it can become a standalone script).
>>
>> This script goes beyond the instructions of the manual on two fronts:
>> - First, it not only tries to build the packages, but also to install
>> them,
>
> I think this is probably the first time we have this problem (that I
> remember of), probably because the Jupyter dependency graph has so many
> propagated inputs.
>
> However, this is definitely something ‘guix lint’ could check with
> something along the lines of the patch below.

I pushed something like that in
993023a28e52c87647fb78a5aa94a524f42ceb71.  It returns what ‘guix
install’ would show, only more concisely (so one has to investigate to
find out what the problem is):

--8<---cut here---start->8---
$ ./pre-inst-env guix lint  -c profile-collisions 
gnu/packages/check.scm:2051:2: python2-pytest-catchlog@1.2.2: propagated inputs 
/gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and 
/gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
gnu/packages/check.scm:2023:2: python2-pytest-warnings@0.2.0: propagated inputs 
/gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and 
/gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
gnu/packages/check.scm:1003:4: python2-pytest-mock@1.10.1: propagated inputs 
/gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and 
/gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
gnu/packages/check.scm:1678:2: python2-pytest-subtesthack@0.1.1: propagated 
inputs /gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and 
/gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
gnu/packages/check.scm:823:2: python2-pytest@4.6.9: propagated inputs 
/gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and 
/gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
gnu/packages/check.scm:888:2: python2-pytest-cov@2.8.1: propagated inputs 
/gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and 
/gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
gnu/packages/check.scm:704:2: python2-nose2@0.9.2: propagated inputs 
/gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and 
/gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
gnu/packages/check.scm:1009:2: python2-pytest-xdist@1.25.0: propagated inputs 
/gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and 
/gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
gnu/packages/check.scm:2028:2: python2-pytest-capturelog@0.7: propagated inputs 
/gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and 
/gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
gnu/packages/check.scm:1603:2: python2-pytest-cache@1.0: propagated inputs 
/gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and 
/gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
gnu/packages/django.scm:251:2: python2-pytest-django@3.1.2: propagated inputs 
/gnu/store/36kb1hx24f819569rpxanj5b9lfl58b3-python2-zipp-1.0.0 and 
/gnu/store/ak123dzl1kv5hb6hp00ga36h65mlvmn3-python2-zipp-1.0.0 collide
gnu/packages/java.scm:7161:2: antlr3@3.5.2: propagated inputs 
java-stringtemplate@3.2.1 and java-stringtemplate@4.0.6 collide
gnu/packages/java.scm:7275:2: antlr3@3.3: propagated inputs antlr3@3.1 and 
antlr3@3.3 collide
gnu/packages/machine-learning.scm:1808:2: python-iml@0.6.2: propagated inputs 
/gnu/store/lpmaa64rpw9a15kh8nw33w51g7qzlsyk-python-matplotlib-3.1.2 and 
/gnu/store/1155r6fr4s7hnjk30gsaz352084hj830-python-matplotlib-3.1.2 collide
gnu/packages/openstack.scm:132:2: python-hacking@1.1.0: propagated inputs 
python-pep8@1.7.0 and python-pep8@1.5.7 collide
gnu/packages/openstack.scm:132:2: python2-hacking@1.1.0: propagated inputs 
python2-pyflakes@2.1.1 and python2-pyflakes@1.2.3 collide
gnu/packages/python-web.scm:1492:2: python-requests@2.20.1: propagated inputs 
python-urllib3@1.24.3 and python-urllib3@1.25.3 collide
gnu/packages/python-xyz.scm:8998:2: python-widgetsnbextension@3.5.1: propagated 
inputs /gnu/store/p7lqxmqskrg7l5fyxpmqvg30f0jhmgxb-python-mistune-0.8.4 and 
/gnu/store/1cgc6k1m0z6ip2adyllsnshix467ggir-python-mistune-0.8.4 collide
gnu/packages/python-xyz.scm:9215:2: jupyter@1.0.0: propagated inputs 
/gnu/store/nba08r6mygpmnrwj1wm01p8fcfgw7sq7-python-ipython-7.9.0 and 
/gnu/store/y0yc4kqgmdipzrqjxjrv98x7rg7bw3rx-python-ipython-7.9.0 collide
gnu/packages/python-xyz.scm:9026:2: python-ipywidgets@7.5.1: propagated inputs 
/gnu/store/p7lqxmqskrg7l5fyxpmqvg30f0jhmgxb-python-mistune-0.8.4 and 
/gnu/store/1cgc6k1m0z6ip2adyllsnshix467ggir-python-mistune-0.8.4 collide
gnu/packages/web.scm:5901:2: python2-pytest-httpbin@0.2.3: 

Re: Using --manfistest with /manifest files

2020-06-14 Thread Ludovic Courtès
Hi,

Pierre Neidhardt  skribis:

> Indeed, that was discussed at length but we still need to reach a
> consensus :)
>
> I personally disagree with the --export-manifest suggestion (which may
> be one of the reasons why this is stalling :p).

Ah, OK.

> Links to the related discussions (lots to read in there!):
>
> - Store channel specification in profile:
>   https://lists.gnu.org/archive/html/guix-devel/2019-11/msg00464.html
>
>   In particular, from there:
>   https://lists.gnu.org/archive/html/guix-devel/2020-02/msg00047.html
>
> While I'm at it, Ludo, if you want to continue the discussion, we've
> left it on Feb 25th with this question from me to you:
>
>> I didn't understand from your previous message which downside you find
>> to embedding the specifications.scm file.  It would save efforts to the
>> user and be more systematic, in the sense that it gives a guarantee to
>> the user that a specifications.scm corresponds to a profile.  This last
>> point, I believe, is crucial.

I think there were several issues we discussed:

  1. We can only approximate that actual profile content; storing
 an approximate ‘manifest.scm’ along with the profile would IMO be
 deceptive.

  2. It’s easy to maintain compatibility over a data format, but it’s
 much harder to maintain compatibility for code.

I think we discussed these issues the best we could in the megathread,
so I’m personally in favor of moving forward in a pragmatic way.

Thanks,
Ludo’.



Re: generate commit messages for package updates

2020-06-14 Thread Ludovic Courtès
Pierre Neidhardt  skribis:

> Is it worth including in guix/etc?

I think it’d be nice!

Ludo’.



Re: [OUTREACHY]: Integration of desktop environments into GNU Guix

2020-06-14 Thread Raghav Gururajan
@Danny

Please find the attached patches.

Corrections:
1) I accidentally left out a patch for glib. I have attached as separate
file. Could you please merge with glib patch while pushing to
wip-desktop? Thanks.
2) There are two two patches named gst-plugins-base. One of them is
gst-plugins-good.

Blog Update:
https://hub.disroot.org/channel/raghavgururajan?f==outreachy

@Others

Please find the following git log.

commit 1a7ac994f1c75879adaed986d3ee9a580e1dbae8
Author: Raghav Gururajan 
Date:   Thu Jun 11 11:30:26 2020 -0400

gnu: gst-plugins-base: Update package definition.

* gnu/packages/gstreamer.scm (gst-plugins-base): Update package
definition.
[arguments]<#:glib-or-gtk?>: New argument.
<#:phases>['disable-tests-for-armhf]: Remove phase.
['disable-failing-tests]: Remove phase.
['patch-docbook-xml]: New phase.
['pre-check]: New phase.
[native-inputs]: Add docbook-xml, gettext-minimal,
gobject-introspection,
gsettings-desktop-schemas, perl, libxml2 and xorg-server-for-tests.
[inputs]: Add bzip2, glib, glib-networking, glu, libgudev, libx11,
libxdamage, libxfixes, libxext, libxshmfence, mesa and v4l-utils.
Remove gst-plugins-base.
[propagated-inputs]: Add gstreamer and gst-plugins-base.
[synopsis]: Modify.
[description]: Modify.

commit 5ab9cf514339d644b1aa2620196ddc08159e29d4
Author: Raghav Gururajan 
Date:   Thu Jun 11 08:40:14 2020 -0400

gnu: gst-plugins-base: Update package definition.

* gnu/packages/gstreamer.scm (gst-plugins-base): Update package
definition.
[outputs]: New output 'doc'.
[arguments]<#:glib-or-gtk?>: New argument.
<#:configure-flags>[-Dgl]: Remove flag.
[-Ddoc]: Remove flag.
<#:phases>['patch]: Remove phase.
['patch-docbook-xml]: New phase.
['patch-tests]: New phase.
['pre-check]: New phase.
['move-doc]: New phase.
[native-inputs]: Add docbook-xml, gettext-minimal, gtk-doc,
gsettings-desktop-
schemas, perl, libxml2 and xorg-server-for-tests.
[inputs]: Add gdk-pixbuf+svg, glu, graphene, gtk+, iso-codes,
libgudev, libjpeg-
turbo, libvisual, libxshmfence, mesa, sdl and wayland. Remove
arguments for opus.
[propagated-inputs]: Add glib-networking. Remove arguments for orc.
[synopsis]: Modify.
[description]: Modify.

commit fe25f5ecac3e725e1738a082aab5353643d9f990
Author: Raghav Gururajan 
Date:   Thu Jun 11 08:12:25 2020 -0400

gnu: Add libvisual-plugins.

* gnu/packages/gstreamer.scm (libvisual-plugins): New variable.

commit 1cec6d61ea70139390b9298e69daa960bc5d1fd4
Author: Raghav Gururajan 
Date:   Thu Jun 11 06:31:26 2020 -0400

gnu: Add esound.

* gnu/packages/gstreamer.scm (esound): New variable.

commit 7a6456c0c2203e43797f02a8198817de6739903f
Author: Raghav Gururajan 
Date:   Thu Jun 11 04:13:59 2020 -0400

gnu: Add libvisual.

* gnu/packages/gstreamer.scm (libvisual): New variable.

commit 47525c79723b9556ac4044b26405291405a67a64
Author: Raghav Gururajan 
Date:   Wed Jun 10 10:32:15 2020 -0400

gnu: gstreamer: Update package definition.

* gnu/packages/gstreamer.scm (gstreamer): Update package definition.
[arguments]<#:glib-or-gtk?>: New argument.
<#:phases>['patch-dockbook-xml]: New phase.
['disable-failing-tests]: Remove phase.
[native-inputs]: Add bash-completion, docbook-xml, docbook-xsl,
gettext-minimal and libxml2.
[inputs]: Add gmp, gsl, gtk+ and libcap.
[propagated-inputs]: Add glib-networking, elfutils and libunwind.
[synopsis]: Modify.
[description]: Modify.

commit d7152fbbd88c298109dc25bdc58d7b08d531b93f
Author: Raghav Gururajan 
Date:   Tue Jun 9 10:14:45 2020 -0400

gnu: gsettings-desktop-schemas: Update package definition.

* gnu/packages/gnome.scm (gsettings-desktop-schemas) [version]:
Update to 3.37.1.
[source][sha256]: Modify base32.
[arguments]<#:glib-or-gtk?>: New argument.
<#:phases>['patch-schemas]: Remove phase.
[native-inputs]: Add gettext-minimal. Remove intltool.
[inputs]: Remove gnome-backgrounds.
[synopsis]: Modify.

commit 718f5ee403075e20dc9f9c25a0ea8e8d9a92bb13
Author: Raghav Gururajan 
Date:   Tue Jun 9 09:44:44 2020 -0400

gnu: graphene: Update package definition.

* gnu/packages/gtk.scm (graphene): Update package definition.
[source][method]: Change from url-fetch to git-fetch.
[uri]: Add git-reference.
[sha256]: Modify base32.
[arguments]<#:glib-or-gtk?>: New argument.
[native-inputs]: Add git-minimal and mutest.

commit ee1ee05ae094010a41ca44bc15761bd8e0f54438
Author: Raghav Gururajan 
Date:   Tue Jun 9 09:43:01 2020 -0400

gnu: Add mutest.

* gnu/packages/check.scm (mutest): New variable.

commit 1e72d7b4078c86b268ed913ce635849f6e291dd5
Author: Raghav Gururajan 
Date:   Tue Jun 9 09:07:54 2020 -0400

gnu: gobject-introspection: Update package definition.

* gnu/packages/glib.scm (gobject-introspection) [version]: Update
to 1.64.1.
[source][sha256]: Modify 

Re: generate commit messages for package updates

2020-06-14 Thread Ricardo Wurmus


Pierre Neidhardt  writes:

> Is it worth including in guix/etc?

In my biased opinion: yes.  I’d like to improve it a little more and
handle more changes, but I think the general approach isn’t going to
change much.

-- 
Ricardo



Re: [PATCH] sql: Add a couple of indexes.

2020-06-14 Thread Christopher Baines

zimoun  writes:

> Hi Chris,
>
> On Sat, 13 Jun 2020 at 17:29, Christopher Baines  wrote:
>
>> I've pushed a rebased version of this patch now. I've also recofigured
>> bayfront to apply these changes. Checking with guix weather, I think it
>> might be helping.
>
> Nice!
>
> What about reconfigure ci.guix.gnu.org and close bug#41708?
>
> http://issues.guix.gnu.org/issue/41708

Indeed, hopefully that can happen soon.

>> → guix weather --substitute-urls=https://bayfront.guix.gnu.org
>
> [...]
>
>>   13.8% (897 out of 6,519) of the missing items are queued
>>   at least 1,000 queued builds
>>   x86_64-linux: 1000 (100.0%)
>>   build rate: 9.34 builds per hour
>>   x86_64-linux: 9.34 builds per hour
>
> I think it is the first I see these results instead of the 504. :-)
> With "guix e782756", it is:
>
> --8<---cut here---start->8---
>   65.7% substitutes available (9,425 out of 14,354)
>   at least 57,816.3 MiB of nars (compressed)
>   97,343.9 MiB on disk (uncompressed)
>   0.010 seconds per request (138.1 seconds in total)
>   103.0 requests per second
>
>   0.0% (0 out of 4,929) of the missing items are queued
>   at least 1,000 queued builds
>   x86_64-linux: 1000 (100.0%)
>   build rate: 9.20 builds per hour
>   x86_64-linux: 9.20 builds per hour
> --8<---cut here---end--->8---
>
> Hum?  Almost 1/3 of substitutes are not available and in the same time
> not queued.  Is it expected?  Does it mean that 1/3 of the builds are
> failing?

Probably not, most likely canceled or a dependency failed to build.

I looked at a recent revision using the Guix Data Service, and it's
unclear [1]. Lots of builds are unknown, and I'm not sure why that would
be.

1: 
http://data.guix.gnu.org/revision/d291b454bd402c88eed1464a1dfa058a2f663874/builds


signature.asc
Description: PGP signature


Re: Cuirass image download

2020-06-14 Thread Mathieu Othacehe


Hey!

> Very nice!  It would be good to have “(ISO-9660)” or similar next to the
> file name.

Thank you :) Fixed with c2aed4a5c1cbed44a9cdf9aab660c4a196a7837d.

> Yes, we could add support for /latest links.

Ok, I'll see what I can do about that.

Thanks,

Mathieu



Re: generate commit messages for package updates

2020-06-14 Thread Ricardo Wurmus

Ricardo Wurmus  writes:

> It is not fully automatic yet as it requires my input to stage
> hunks, but the commit messages it produces take all input changes into
> account, which is something the “update” yasnippet does not do.

Attached is the fully automatic version.

You just make your changes and run the tool.  It will stage all diffs
that are associated with the same S-expression, generate the commit
message, and make the commit for each S-expression.

Note that it probably doesn’t do the right thing when something other
than a package expression is modified (e.g. a copyright line).

-- 
Ricardo



committer.scm
Description: Binary data