Re: gnome-updates

On Wed, May 24, 2017 at 10:17:22PM +0200, Marius Bakke wrote: > Leo Famulari writes: > > > On Sun, May 14, 2017 at 05:35:15PM +0200, Marius Bakke wrote: > >> Instead I merged an older revision of this branch to 'staging' and > >> cherry-picked the latest patches. @Leo, are you able to start it la

Re: gnome-updates

Leo Famulari writes: > On Sun, May 14, 2017 at 05:35:15PM +0200, Marius Bakke wrote: >> Instead I merged an older revision of this branch to 'staging' and >> cherry-picked the latest patches. @Leo, are you able to start it later >> today? Please wait for a mesa update, coming soonish :-) > > Star

Re: gnome-updates

On Sun, May 14, 2017 at 05:35:15PM +0200, Marius Bakke wrote: > Instead I merged an older revision of this branch to 'staging' and > cherry-picked the latest patches. @Leo, are you able to start it later > today? Please wait for a mesa update, coming soonish :-) Started! signature.asc Descriptio

Re: gnome-updates

Ludovic Courtès writes: > Hello Kei, > > k...@openmailbox.org (Kei Kebreau) skribis: > >> kkebreau pushed a change to branch gnome-updates >> in repository guix. > > I don’t see a ‘gnome-updates’ jobset on hydra.gnu.org. Is anyone taking > care of it? It would be nice to merge this branch event

Re: Gnome-updates

On Tue, May 03, 2016 at 01:35:49PM +0200, Ludovic Courtès wrote: > It’s building now. Once most of it is built on x86_64, we should look > at the diff against master in Hydra and check for any regressions. There is a problem with a simple solution, I think: http://hydra.gnu.org/build/1187760/n

Re: Gnome-updates

On Tue, May 03, 2016 at 08:32:29PM +0300, Efraim Flashner wrote: > On Tue, May 03, 2016 at 12:38:58AM +, 宋文武 wrote: > > Current poppler is 0.42.0 in gnome- updates, I think when merge back into > > master, with conflict resolved it will undo the graft. Do you mean we > > resolve it explicitl

Re: Gnome-updates

On Tue, May 03, 2016 at 12:38:58AM +, 宋文武 wrote: > Current poppler is 0.42.0 in gnome- updates, I think when merge back into > master, with conflict resolved it will undo the graft. Do you mean we > resolve it explicitly in gnome-updates? That's better, thanks! And perhaps > we could updat

Re: Gnome-updates

iyzs...@member.fsf.org (宋文武) skribis: > l...@gnu.org (Ludovic Courtès) writes: [...] >>> - Skip 'test_utf8_inout' of gjs. >>> it fails with gobject-introspection-1.48.0, but use python3 to >>> call the test in Regress.typelib will pass. Report as: >>>

Re: Gnome-updates

Current poppler is 0.42.0 in gnome- updates, I think when merge back into master, with conflict resolved it will undo the graft. Do you mean we resolve it explicitly in gnome-updates? That's better, thanks! And perhaps we could update it to the lastest 0.43.0?

Re: Gnome-updates

On Mon, May 02, 2016 at 10:47:16PM +0800, 宋文武 wrote: > Thanks for the review. > I have rebase it upon master again with the one log change but > leave out the poppler CVE-2015-8868 fix (it's in 0.42.0) in master. > (I can't use force push so I delete and push it again..) I'm just joining this conv

Re: Gnome-updates

l...@gnu.org (Ludovic Courtès) writes: > Hello! > > iyzs...@member.fsf.org (宋文武) skribis: > >> - Disable a failing rtprtx test of gst-plugins-good. >> I can pass it using `guix environment', but fail with `guix build'. > > The log for this commit contains a typo: it doesn’t mention the variable

Re: Gnome-updates

Hello! iyzs...@member.fsf.org (宋文武) skribis: > - Disable a failing rtprtx test of gst-plugins-good. > I can pass it using `guix environment', but fail with `guix build'. The log for this commit contains a typo: it doesn’t mention the variable name, only the ‘arguments’ field. Also, could you

Re: Gnome-updates

Hi, I have rebase it upon mastet, update more packages to their latest, and test on my x86_64 laptop with 'gnome-desktop-service'. It seems work fine so far. And here are some 'questionable' changes: - Disable a failing rtprtx test of gst-plugins-good. I can pass it using `guix environment', bu

Re: Gnome-updates

Hello! Regarding the gjs failure worked around by commit 63e7796f626ee40b8259ce56b93f5596e8a1f8c5, I briefly investigated. Upon failure, the ‘stderr.log’ file reads: --8<---cut here---start->8--- Gjs-Message: JS LOG: Expected nonconst ♥ utf8 (string) but was

Re: Gnome-updates

iyzs...@member.fsf.org (宋文武) skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> Andreas Enge skribis: >> >>> the gnome-updates branch has built on x86, and compared to master, there are >>> not that many regressions: >>>http://hydra.gnu.org/eval/108921?compare=master#tabs-now-fail >> >> I

Re: Gnome-updates

l...@gnu.org (Ludovic Courtès) writes: > Andreas Enge skribis: > >> the gnome-updates branch has built on x86, and compared to master, there are >> not that many regressions: >>http://hydra.gnu.org/eval/108921?compare=master#tabs-now-fail > > In fact this slightly overestimates the failures c

Re: Gnome-updates

Andreas Enge skribis: > the gnome-updates branch has built on x86, and compared to master, there are > not that many regressions: >http://hydra.gnu.org/eval/108921?compare=master#tabs-now-fail In fact this slightly overestimates the failures compared to master; in particular, all the Octave/

Re: GNOME updates

iyzs...@member.fsf.org (宋文武) skribis: > Hi! With the help of ‘guix refresh -t gnome’ I update many GNOME > packages to latest (the 3.20 release) in the ‘gnome-updates’ branch. > > Also: > glib: Disable tests in build phases instead of patches. > gtk+: Enable SVG support. (by using gdk-pixbuf+