all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Timothy Sample <samplet@ngyro.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: GNOME 3.30
Date: Mon, 06 May 2019 00:40:03 -0400	[thread overview]
Message-ID: <87pnow5h7g.fsf@ngyro.com> (raw)

Hi Ricardo,

I am testing the GNOME 3.30 branch now (on real hardware), and it works
quite well.  The only issue I’m seeing is that the clock is wrong.  That
is, running “date” gives me the correct time in my timezone, but the
GNOME Shell clock seems to be showing UTC.  If I try to change it,
nothing happens.

Beyond that, I noticed that GNOME Session was still at 3.28.  I wrote a
little script to find the packages that are behind GNOME 3.30.2.  Here’s
the packages that should be upgraded:

    baobab: 3.28.0 → 3.30.0
    cheese: 3.28.0 → 3.30.0
    file-roller: 3.28.0 → 3.30.1
    font-abattis-cantarell: 0.0.25 → 0.111
    gedit: 3.28.1 → 3.30.2
    gjs: 1.52.3 → 1.54.2
    gnome-backgrounds: 3.28.0 → 3.30.0
    gnome-bluetooth: 3.28.0 → 3.28.2
    gnome-calendar: 3.28.2 → 3.30.0
    gnome-clocks: 3.28.0 → 3.30.1
    gnome-control-center: 3.28.2 → 3.30.1
    gnome-screenshot: 3.26.0 → 3.30.0
    gnome-session: 3.28.1 → 3.30.1
    gnome-shell-extensions: 3.28.1 → 3.30.1
    gom: 0.3.2 → 0.3.3
    graphene: 1.6.0 → 1.8.2
    grilo-plugins: 0.3.3 → 0.3.8
    grilo: 0.3.3 → 0.3.6
    gtk-doc: 1.28 → 1.29
    orca: 3.28.1 → 3.30.1
    python-pyatspi: 2.26.0 → 2.30.0
    python-pygobject: 3.28.3 → 3.30.1
    simple-scan: 3.24.1 → 3.30.2
    tracker: 2.0.4 → 2.1.5
    zenity: 3.28.1 → 3.30.0

Unless you have a reason to leave them behind, I will try and update
them.


-- Tim

             reply	other threads:[~2019-05-06  4:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06  4:40 Timothy Sample [this message]
2019-05-06  7:10 ` GNOME 3.30 Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pnow5h7g.fsf@ngyro.com \
    --to=samplet@ngyro.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.