Ricardo Wurmus <[email protected]> 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.
