Hi,
How to reproduce the issue? May you, please provide some steps please.
--
… наш разум - превосходная объяснительная машина которая способна
найти смысл почти в чем угодно, истолковать любой феномен, но
совершенно не в состоянии принять мысль о непредсказуемости.
Am Dienstag, dem 09.05.2023 um 20:12 +0100 schrieb Bruno Victal:
> Hi Ludo’,
>
> On 2023-02-25 17:46, Ludovic Courtès wrote:
> > Bruno Victal skribis:
> > > In [1], the issue arises from using activation-service-type to
> > > create files/directories for services
> > > when these should be
Hi,
"bdju" via Bug reports for GNU Guix writes:
> guix (GNU Guix) e0c35d1578c10a8fe27c8372f3a8bb5dd88b01b8
> guix system
> hikari build log attached
I tried to look into it before the core-updates merge, but it seems that
hikari is not maintained anymore, so I don't expect it to work with
Gtk:ERROR:gtkiconhelper.c:494:
ensure_surface_for_gicon: assertion
failed (error == NULL): Failed to load
/run/current-system/profile/share/icons/Adwaita/16x16/status/image-missing.png:
Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Bail out!
Hi Andreas,
Andreas Enge writes:
> When working on a branch and deciding whether to merge it, we need a way
> of comparing its status with that of the master branch. As far as I can see,
> there is currently no way in cuirass to compare arbitrary evaluations and
> get a list (or a dashboard) of
guix (GNU Guix) e0c35d1578c10a8fe27c8372f3a8bb5dd88b01b8
guix system
hikari build log attached
WARNING: (guile-user): imported module (guix build utils) overrides core
binding `delete'
starting phase `set-SOURCE-DATE-EPOCH'
phase `set-SOURCE-DATE-EPOCH' succeeded after 0.0 seconds
starting phase
GNOME "tracker" is built with "libexecdir" in its own prefix in the store and
"tracker-miners" in its own. The problem is that "tracker" does not have access
to the executable files in the "libexecdir" of "tracker-miners", so commands
like "tracker3 extract file.flac" does not work. Due to this
Hi Arun,
Arun Isaac writes:
> Hi Maxim,
>
> When a patch relates to no teams, I get the empty header output
> "X-Debbugs-Cc: ". For such patches, it would be nicer to not add any
> header instead of adding an empty header.
Good catch! Fixed.
>> +(define (team->members team)
>> + "Return the
Ludovic Courtès writes:
> Hi,
>
> Christopher Baines skribis:
>
>> It seems to build for me, but I'm having problems cross building. There
>> were warnings before about protocol/ssl3 being undefined, but now this
>> seems to result in an error when building extra.scm:
>>
>>
>> GUILEC
Hi,
Christopher Baines skribis:
> It seems to build for me, but I'm having problems cross building. There
> were warnings before about protocol/ssl3 being undefined, but now this
> seems to result in an error when building extra.scm:
>
>
> GUILEC modules/gnutls.go
> gnutls.scm:608:23:
Andreas Enge writes:
> Cuirass should sort builds and only offload derivations for which all
> inputs are available.
...
> Alternatively, build jobs could be sorted topologically and then be kept
> in a list; then before sending out a job, all its inputs have been tried
> to be built; the job
Christopher Baines writes:
> Since the recent core-updates merge, I've seen the build coordinator
> using less memory, but it's also been crashing in a new way, up to 10
> times a day.
>
> In the log, you see something like:
>
> 2023-05-07 09:15:42 Signals delivery fails constantly at GC
Hi,
zimoun writes:
> Dear Danny,
>
> You asked on guix-devel since when Mesa is not reproducible: at least
> since v1.1.0.
>
> git --no-pager log v1.1.0 -1 --format='%H'
> d62c9b2671be55ae0305bebfda17b595f33797f2
>
> guix time-machine --commit=d62c9b2671be55ae0305bebfda17b595f33797f2 \
>
When working on a branch and deciding whether to merge it, we need a way
of comparing its status with that of the master branch. As far as I can see,
there is currently no way in cuirass to compare arbitrary evaluations and
get a list (or a dashboard) of builds that fail in one, but not the other.
Stopping and starting builds in cuirass is not very comfortable.
When working on core-updates, I stopped builds for some old evaluations
on aarch64, where our build power would not be enough, assuming that many
of the old builds were made obsolete by newer changes. (For instance,
these could be
This is a wishlist bug, but it is important for architectures where we
are currently short on build power, and where this issue can stall builds
and waste an arbitrary amount of build power.
Cuirass should sort builds and only offload derivations for which all
inputs are available.
In my current
16 matches
Mail list logo
