Re: GNOME updater

[Ludovic Courtès]

Efraim Flashner <address@hidden> skribis:

> A for gnome-3, the 3.19 series AFAIK is the beta/development releases for
> 3.20, so would we want to update to those numbers?

Good point, we probably don’t want those.

Fixed in c499125, which leads to a shorter list:

--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix refresh -t gnome 
gnu/packages/mail.scm:211:13: gmime would be upgraded from 2.6.19 to 2.6.20
gnu/packages/gtk.scm:852:13: atkmm would be upgraded from 2.24.1 to 2.24.2
gnu/packages/gnome.scm:1612:13: seahorse would be upgraded from 3.16.0 to 3.18.0
gnu/packages/gnome.scm:1340:13: libgnomeprintui would be upgraded from 2.8.2 to 
2.18.6
gnu/packages/gnome.scm:3373:13: epiphany would be upgraded from 3.16.3 to 3.18.1
gnu/packages/gnome.scm:331:13: gnome-keyring would be upgraded from 3.16.0 to 
3.18.3
gnu/packages/gnome.scm:4196:13: network-manager-applet would be upgraded from 
1.0.6 to 1.0.8
gnu/packages/gnome.scm:837:13: librsvg would be upgraded from 2.40.11 to 2.40.12
gnu/packages/gnome.scm:3538:13: yelp-tools would be upgraded from 3.16.1 to 
3.18.0
gnu/packages/gnome.scm:3691:13: file-roller would be upgraded from 3.10.0 to 
3.16.4
gnu/packages/gnome.scm:1517:13: gnumeric would be upgraded from 1.12.17 to 
1.12.24
gnu/packages/gnome.scm:2764:13: clutter-gst would be upgraded from 3.0.6 to 
3.0.14
gnu/packages/gnome.scm:1762:13: dconf would be upgraded from 0.22.0 to 0.24.0
gnu/packages/gnome.scm:2941:13: grilo-plugins would be upgraded from 0.2.14 to 
0.2.16
gnu/packages/gnome.scm:3237:13: gvfs would be upgraded from 1.24.1 to 1.26.2
gnu/packages/gnome.scm:2553:13: aisleriot would be upgraded from 3.16.1 to 
3.18.2
gnu/packages/gnome.scm:2795:13: libchamplain would be upgraded from 0.12.10 to 
0.12.12
gnu/packages/gnome.scm:3479:13: yelp-xsl would be upgraded from 3.16.1 to 3.18.1
gnu/packages/gnome.scm:2074:13: libsecret would be upgraded from 0.18 to 0.18.3
gnu/packages/gnome.scm:2736:13: clutter-gtk would be upgraded from 1.6.0 to 
1.6.6
gnu/packages/gnome.scm:587:13: adwaita-icon-theme would be upgraded from 3.16.2 
to 3.18.0
gnu/packages/gnome.scm:1460:13: goffice would be upgraded from 0.10.14 to 
0.10.24
gnu/packages/gnome.scm:398:13: evince would be upgraded from 3.18.1 to 3.18.2
gnu/packages/gnome.scm:300:13: libgnome-keyring would be upgraded from 3.6.0 to 
3.12.0
gnu/packages/gnome.scm:2326:13: geocode-glib would be upgraded from 3.16.0 to 
3.18.0
gnu/packages/gnome.scm:2993:13: totem would be upgraded from 3.16.1 to 3.18.1
gnu/packages/gnome.scm:1302:13: libgnomeprint would be upgraded from 2.8.2 to 
2.18.8
gnu/packages/gnome.scm:2589:13: devhelp would be upgraded from 3.16.1 to 3.18.1
gnu/packages/gnome.scm:2890:13: grilo would be upgraded from 0.2.12 to 0.2.14
gnu/packages/gnome.scm:774:13: libcroco would be upgraded from 0.6.8 to 0.6.9
gnu/packages/gnome.scm:155:13: gnome-common would be upgraded from 3.14.0 to 
3.18.0
gnu/packages/gnome.scm:2462:13: gnome-settings-daemon would be upgraded from 
3.16.0 to 3.18.2
gnu/packages/glib.scm:409:13: libsigc++ would be upgraded from 2.6.1 to 2.6.2
--8<---------------cut here---------------end--------------->8---

> Also, if we don't want to use those releases, we should check if the
> other packages also use the odd (version minor-version) numbers as a
> symbol for beta/rc releases.

This is checked for GNU packages already, and I assume there’s no notion
of “unstable” releases on repos such as PyPI and CRAN?

Thanks for your feedback!

Ludo’.