Hello,
Ludovic Courtès writes:
> Hi,
>
> Maxim Cournoyer skribis:
>
>> In case you hadn't taken notice, the core-update-frozen branch was
>> finally merged into master. So please reconfigure your remotes to avoid
>> uploading any further work there :-).
>
> I’m late to the party, but that’s
Hi,
Maxim Cournoyer skribis:
> In case you hadn't taken notice, the core-update-frozen branch was
> finally merged into master. So please reconfigure your remotes to avoid
> uploading any further work there :-).
I’m late to the party, but that’s because I’ve been contemplating my
updated
Am 14.12.21 um 09:15 schrieb zimoun:
Now, core-updates-frozen is merged, they can go to master. :-)
I pushed the fixes to master yesterday. Shall I cherry-pick them to the
release-1.4 branch or will somebody else take care of that?
--
Regards
Hartmut Goebel
| Hartmut Goebel
Hello!
Em segunda-feira, 13 de dezembro de 2021, às 22:34:34 -03, Maxim Cournoyer
escreveu:
> Hello Guix!
>
> In case you hadn't taken notice, the core-update-frozen branch was
> finally merged into master.
Hooray! Thank you very much to everyone who made this happen! I really
appreciate the
Ricardo Wurmus skribis:
> Ricardo Wurmus writes:
>
>> Unfortunately, this is not enough to build tensorflow. At the very end
>> we have this problem: […]
>
> This should now be fixed with commit e1c91aae23af12bccab615902a08ebc86defc1ac.
Thanks!
signature.asc
Description: PGP signature
Ricardo Wurmus writes:
> Unfortunately, this is not enough to build tensorflow. At the very end
> we have this problem: […]
This should now be fixed with commit e1c91aae23af12bccab615902a08ebc86defc1ac.
--
Ricardo
Hey Simon!
zimoun writes:
> Hi Maxim,
>
> On Mon, 13 Dec 2021 at 22:20, Maxim Cournoyer
> wrote:
>
>> It'll have to be resolved on core-updates :-).
>
> Well, Julia update can happen in master, IMHO. Even, depending on the
> release date, it appears to me doable for the next release. ;-)
Oh
ently released 1.7.3 would be nice to fix the
spurious warnings. [1]
[0] https://issues.guix.gnu.org/52269
[1] https://lists.x.org/archives/xorg-announce/2021-December/003120.html
Thanks all for the great collaboration that went into readying
core-updates-frozen for the merge! :-)
Maxim
Congratulations, everyone!
I love Guix, and I really appreciate all the work that everyone puts into it.
I'm updating now :)
Sincerely,
--
Katherine
Hi Josselin,
On Tue, 14 Dec 2021 at 14:24, Josselin Poiret wrote:
> What exactly would those "release-specific enhancements" be?
Basically,
- Fix important bugs and/or blocking ones (I do not know if there are
many today). And previous release, a "release" bug had been opened to
collect
Hi,
> [[PGP Signed Part:Undecided]]
> guix-comm...@gnu.org skribis:
>
>> rekado pushed a change to branch core-updates-frozen
>> in repository guix.
>>
>> new d503194 gnu: python2-entrypoints: Add missing input.
>> new 672c7a2 gnu: tensorflo
Maxim Cournoyer writes:
> In case you hadn't taken notice, the core-update-frozen branch was
> finally merged into master. So please reconfigure your remotes to avoid
> uploading any further work there :-).
Great work and thanks for coordinating it! Thanks also to everyone who
contributed :)
guix-comm...@gnu.org skribis:
> rekado pushed a change to branch core-updates-frozen
> in repository guix.
>
> new d503194 gnu: python2-entrypoints: Add missing input.
> new 672c7a2 gnu: tensorflow: Do not unpack directory.
> new 6d3439b gnu: eigen-for-tensorfl
ush them to core-updates-frozen and
> or to master?
Now, core-updates-frozen is merged, they can go to master. :-)
However, because ’format-patch’ had been used without the ’--base’
option, and because the Git tree changed, I cannot apply and test your
patches.
Could you rebase them? I have n
Hey,
> That's it! Enjoy the latest additions and improvements, and report any
> issues you encounter!
That's great news! Thanks to all the people that have been involved and
special thanks to you Maxim for your commitment.
Mathieu
Hi Maxim,
On Mon, 13 Dec 2021 at 22:20, Maxim Cournoyer wrote:
> It'll have to be resolved on core-updates :-).
Well, Julia update can happen in master, IMHO. Even, depending on the
release date, it appears to me doable for the next release. ;-)
Cheers,
simon
Hi,
On Mon, 13 Dec 2021 at 20:34, Maxim Cournoyer wrote:
> In case you hadn't taken notice, the core-update-frozen branch was
> finally merged into master. So please reconfigure your remotes to avoid
> uploading any further work there :-).
>
> A tentative release preparation branch
Hi Maxim,
Maxim Cournoyer writes:
> In case you hadn't taken notice, the core-update-frozen branch was
> finally merged into master. So please reconfigure your remotes to avoid
> uploading any further work there :-).
>
> [...]
>
> That's it! Enjoy the latest additions and improvements, and
Hi Simon,
zimoun writes:
> Hi,
>
> First, I am not convinced that upgrade Julia from 1.6.3 to 1.6.4 is
> something to do now; especially when the branch is “frozen”. Using
> patches #52117 [1], all failures are fixed for 1.6.3.
>
> 1: https://issues.guix.gnu.org/52117
>
>
> Here a rough
Hello Guix!
In case you hadn't taken notice, the core-update-frozen branch was
finally merged into master. So please reconfigure your remotes to avoid
uploading any further work there :-).
A tentative release preparation branch 'version-1.4.0' was then created
from master, where
Hi,
zimoun writes:
> After some Cuirass monitoring and restarted some unexpected failures,
> the situation for ghc-* on i686-linux is the same as the one from
> current master.
I took a few minutes to triage these. Most of them are fixable.
> Two packages are broken in core-up
Hi,
All related Haskell packages for both x86_64 and i686 in
core-updates-frozen are not blockers for the merge. \o/
After some Cuirass monitoring and restarted some unexpected failures,
the situation for ghc-* on i686-linux is the same as the one from
current master.
Two packages are broken
Hi,
I just sent in patches fixing this issue, see
<http://debbugs.gnu.org/cgi/bugreport.cgi?bug=52259>
They can be added on master, too, since they are not dealing with
'sanitiy-check
Question: After approval, shall I push them to core-updates-frozen and
or to master?
--
Regards
H
Hi,
TL;DR: I'll take care of this within the next few days.
Am 01.12.21 um 17:44 schrieb zimoun:
Many thanks for providing this info and the links.
The issue with 'trythond-*' is the new phase `sanity-check' for
python-build-system.
The way trytond modules are intended (by the
Hi,
The branch core-updates-frozen will be merged soon. Among some
breakage here or there, one block of broken packages is about 'tryton'
[1]: each points are sorted by alphabetical order, and the mouse on
the red point should provide the name of the package, then click leads
to the evaluation
Hi,
First, I am not convinced that upgrade Julia from 1.6.3 to 1.6.4 is
something to do now; especially when the branch is “frozen”. Using
patches #52117 [1], all failures are fixed for 1.6.3.
1: https://issues.guix.gnu.org/52117
Here a rough attempt which replaces the source of 1.6.3 by
Hi,
On Thu, 25 Nov 2021 at 03:13, zimoun wrote:
> I am currently rebuilding all the julia-* packages. It is high probable
> some are now broken. But it appears to me not a blocker for the
> merge.
All is fixed in patch#52117 [1]. After this hacking session,
1. The package julia uses
. You may need to disable a whole test suite
> of
> similarly faulted tests, if they all behave the same.
After this hacking day, Julia builds deterministically* on
core-updates-frozen. Along the way, now the test suite runs in parallel
which reduces a lot the feedback loop. :-) And a variant
Hi Josselin,
Josselin Poiret writes:
> Maxim Cournoyer writes:
>
> at it throws, after adding the missing polkit export:
>>
>> --8<---cut here---start->8---
>> $ ./pre-inst-env guix build -s aarch64-linux gnome-control-center -n
>> guix build: error:
Hi,
On Mon, 22 Nov 2021 at 15:13, Maxim Cournoyer wrote:
> 2. Disable the problematic tests. You may need to disable a whole test suite
> of
> similarly faulted tests, if they all behave the same.
I am becoming crazy… For instance this test randomly* fails:
@test mul!(C, vf,
Maxim Cournoyer writes:
at it throws, after adding the missing polkit export:
>
> --8<---cut here---start->8---
> $ ./pre-inst-env guix build -s aarch64-linux gnome-control-center -n
> guix build: error: gnu/packages/gnome.scm:5299:2: package
>
Hi Thiago,
Thiago Jung Bauermann writes:
[...]
> IIUC it’s a bug to test (%current-system) before
> (%current-target-system). That’s because the latter is only defined
> for cross-builds, while the former is always defined. So in practice
> (%current-target-system) will never be checked.
Oh,
nst-env guix build -s aarch64-linux gnome-control-center -n
guix build: error: gnu/packages/gnome.scm:5299:2: package
`colord-minimal@1.4.5' has an invalid input: ("polkit" #)
--8<---cut here---end------->8---
I don't see how it's different from
ments is on my todo list.
> Are we done and ready for merging once this patch has been applied to
> ‘core-updates-frozen’?
Hooray! I’m currently investigating a problem with lualatex (issue 51252).
I don’t know whether it’s serious enough to delay the merge.
--
Thanks,
Thiago
Are we done and ready for merging once this patch has been applied to
‘core-updates-frozen’?
Thanks,
Ludo’.
Hello again,
I've now tried this:
--8<---cut here---start->8---
gnu: polkit: Define polkit package variable based on architecture.
* gnu/packages/polkit.scm (polkit): Rename to...
(polkit*): ... this.
(polkit-duktape): Adjust to inherit from polkit*.
Hi Ludovic,
Ludovic Courtès writes:
> Hi Maxim,
>
> Maxim Cournoyer skribis:
>
>> +;;; Define a top level polkit variable that can be built on any of the
>> +;;; supported platforms. This is to work around the fact that our
>> +;;; mrustc-bootstrapped rust toolchain currently only supports
Hello,
zimoun writes:
> Hi Ludo,
>
> On Mon, 22 Nov 2021 at 14:21, Ludovic Courtès wrote:
>
>> >> … there’s probably more.
>
> Julia is annoying, Because the test suite sometimes passes, sometimes
> not. Well, I am not even sure it is the same part that fails. I
> notice that "guix build
Ludovic Courtès writes:
Hi,
Ricardo Wurmus skribis:
on the core-updates-frozen branch we have a minor problem:
python-numpy has been upgraded to 1.21, but python-numba can
only
be built with 1.20[1]. I added python-numpy-1.20 and made
python-numba use it.
How big of an effort would
Hi,
Ludovic Courtès writes:
Ricardo Wurmus skribis:
on the core-updates-frozen branch we have a minor problem:
python-numpy has been upgraded to 1.21, but python-numba can
only
be built with 1.20[1]. I added python-numpy-1.20 and made
python-numba use it.
How big of an effort would
Hi Ludo,
On Mon, 22 Nov 2021 at 14:21, Ludovic Courtès wrote:
> >> … there’s probably more.
Julia is annoying, Because the test suite sometimes passes, sometimes
not. Well, I am not even sure it is the same part that fails. I
notice that "guix build julia --without-tests=julia" then "guix
Hi Maxim,
Maxim Cournoyer skribis:
> +;;; Define a top level polkit variable that can be built on any of the
> +;;; supported platforms. This is to work around the fact that our
> +;;; mrustc-bootstrapped rust toolchain currently only supports the x86_64
> +;;; architecture...
>
Hi,
Ricardo Wurmus skribis:
> on the core-updates-frozen branch we have a minor problem:
> python-numpy has been upgraded to 1.21, but python-numba can only
> be built with 1.20[1]. I added python-numpy-1.20 and made
> python-numba use it.
How big of an effort would it be to mod
I see you fixed a bunch of them, yay!
> That said, it’s amazing how much progress we made in so little time!
> I’ll continue to prioritize core-updates-frozen for the next few days.
Yes, let’s do that. I’ve fixed things I’ll probably never ever use,
like trytond. A call to everyone t
Hello,
Ludovic Courtès writes:
> Hi,
>
> Thiago Jung Bauermann skribis:
>
>> Em quinta-feira, 11 de novembro de 2021, às 15:23:37 -03, Maxim Cournoyer
>> escreveu:
>>> Hello Guix!
>>>
>>> I've finally merged the core-updates-frozen-batche
Hi Ricardo,
On Sat, 20 Nov 2021 at 10:42, Ricardo Wurmus wrote:
> on the core-updates-frozen branch we have a minor problem:
> python-numpy has been upgraded to 1.21, but python-numba can only
> be built with 1.20[1]. I added python-numpy-1.20 and made
> python-numba use
Lars-Dominik Braun writes:
Hello Ricardo,
So… since numpy 1.20 is the exception here, could we perhaps …
rename it? And then have python-numba import that renamed
module
“totally-not-numpy” instead of “numpy”? Could we thus avoid
this
conflict? If renaming is an option — how would
Hello Ricardo,
> So… since numpy 1.20 is the exception here, could we perhaps …
> rename it? And then have python-numba import that renamed module
> “totally-not-numpy” instead of “numpy”? Could we thus avoid this
> conflict? If renaming is an option — how would it be done? Is it
> enough
Hi Guix,
on the core-updates-frozen branch we have a minor problem:
python-numpy has been upgraded to 1.21, but python-numba can only
be built with 1.20[1]. I added python-numpy-1.20 and made
python-numba use it.
Now the problem I have is that numba is used with other packages
little
time! I’ll continue to prioritize core-updates-frozen for the
next few days.
Nov. 23th will mark Guix’s 9th birthday. Wouldn’t it be great
to have
that branch finally merged in ‘master’ by then?
Sounds doable, let’s keep up the good work!
I hope we can make it!
--
Ricardo
Hi there!
Ludovic Courtès skribis:
> I hereby declare tomorrow, Thursday Nov. 18th, day of the on-line
> ‘core-updates-frozen’ sprint!
I’d like to congratulate ourselves and call it a success! A dedicated
group worked all day long anywhere-on-earth and pushed 79 commits fixing
a v
Ludovic Courtès writes:
I hereby declare tomorrow, Thursday Nov. 18th, day of the
on-line
‘core-updates-frozen’ sprint!
The idea is that you join #guix on IRC, you try to build your
system or
profile from ‘core-updates-frozen’, and you report (and fix!)
any issues
you may have
Hello Guix!
I hereby declare tomorrow, Thursday Nov. 18th, day of the on-line
‘core-updates-frozen’ sprint!
The idea is that you join #guix on IRC, you try to build your system or
profile from ‘core-updates-frozen’, and you report (and fix!) any issues
you may have, in the warmth of a collective
Hi!
Vagrant Cascadian skribis:
> I've now pushed to core-updates-frozen:
>
>
> https://git.savannah.gnu.org/cgit/guix.git/commit/?h=core-updates-frozen=6cdf4e5bf230fdbe17e592c2ec74fb34dba70eb5
Thanks!
>> I'll also make a plea to create a "make dist" job on ci.gu
Hi,
Thiago Jung Bauermann skribis:
> Em quinta-feira, 11 de novembro de 2021, às 15:23:37 -03, Maxim Cournoyer
> escreveu:
>> Hello Guix!
>>
>> I've finally merged the core-updates-frozen-batched-changes to
>> core-updates-frozen.
>
> Hooray!
>
&
On 2021-11-14, Vagrant Cascadian wrote:
> There is a very long patch in core-updates-frozen for the gd package
> which breaks "make dist" ... and about 10k packages are transitively
> dependent on gd... so this seems (at least to me) really important to
> fix before merging i
Heads up for anyone working on merging core-updates-frozen into master!
There is a very long patch in core-updates-frozen for the gd package
which breaks "make dist" ... and about 10k packages are transitively
dependent on gd... so this seems (at least to me) really important to
Hello Maxim,
Em quinta-feira, 11 de novembro de 2021, às 15:23:37 -03, Maxim Cournoyer
escreveu:
> Hello Guix!
>
> I've finally merged the core-updates-frozen-batched-changes to
> core-updates-frozen.
Hooray!
> One thing we could do in the meantime is to replace our
Hello Guix!
I've finally merged the core-updates-frozen-batched-changes to
core-updates-frozen. One of the changes it brought is an updated
(non-grafted) polkit; this polkit now depends on mozjs@78 which itself
depends on rust.
Unfortunately, our rust bootstrap doesn't currently build
Hey Ricardo,
> It should be fine now. I didn’t run the test myself, but I ran most of the
> commands and found a few more hardcoded tool file names that referenced /sbin
> or /usr/bin.
Yes, I confirm it passes! I also fixed the childhurd test. Only 9 tests
to go :).
Thanks,
Mathieu
Hi Mathieu,
I fixed the build. Also had to upgrade 389-ds-base to get
around a linker
error.
Thanks for your support here! The ldap test is now run, but
sadly there
are some failures: https://ci.guix.gnu.org/build/928047/log/raw.
Thanks for checking!
It should be fine now. I didn’t
Hello Ricardo,
> I fixed the build. Also had to upgrade 389-ds-base to get around a linker
> error.
Thanks for your support here! The ldap test is now run, but sadly there
are some failures: https://ci.guix.gnu.org/build/928047/log/raw.
Mathieu
Hey,
> For example, this evaluation from Sep 17 has thousands of scheduled
> evaluations:
>
> https://ci.guix.gnu.org/eval/19271?status=pending
Mmmh, not nice. Any chance you could share the cuirass-remote-worker
logs on the guixp9 machine?
Thanks,
Mathieu
Mathieu Othacehe writes:
* ldap (https://ci.guix.gnu.org/build/901179/details)
=> 389-ds-base build appears to be broken.
I fixed the build. Also had to upgrade 389-ds-base to get around
a linker error.
--
Ricardo
build is now affected by an issue that I only
noticed yesterday: powerpc64le-linux builds for core-updates-frozen get
permanently stuck in the ‘Scheduled’ state, even though guixp9 is
completely idle (as it is right now).
For example, this evaluation from Sep 17 has thousands of scheduled
e
Hey Thiago,
> I was waiting for this world rebuild to happen to see the results in
> Cuirass now that powerpc64le-linux builds are only done on guixp9, but in
> hindsight it would have been better if I requested that those builds were
> restarted instead. Restarting this build should remove
On Tue, Sep 28, 2021 at 01:57:45PM +0200, Ludovic Courtès wrote:
> Hello Guix!
>
> Wouldn’t it be nice to get ‘core-updates-frozen’ merged? :-)
>
> What about merging the patches blocked by
> <https://issues.guix.gnu.org/50358>? We could even have them on a
> se
Hello Ludo,
Em terça-feira, 28 de setembro de 2021, às 08:57:45 -03, Ludovic Courtès
escreveu:
> Hello Guix!
>
> Wouldn’t it be nice to get ‘core-updates-frozen’ merged? :-)
>
> What about merging the patches blocked by
> <https://issues.guix.gnu.org/50358>?
Hey!
> have more system tests passing. Currently 16 out of 87 are
> broken. Except for the nfs-root-fs that has always been broken, the
> other tests probably cover user configurations out there.
Made some progress here but there are still a bit more work needed:
* childhurd
Hi Ludo’ and Guixers,
Thanks for the good progress on core-updates-frozen (where I'm currently
writing from and have nearly everything working as before). Seems like we have
a few different bug numbers and threads for the world rebuild. Sorry for
repeating from #50860, which I will paste below
Could this patch be reviewed please? It's needed to build strace from
core-updates-frozen on AArch64 and it would be good to get it applied
ahead of the merge.
It wasn't sent out to guix-patches and I think it got missed.
http://issues.guix.gnu.org/50346#7
--
Simon South
si...@simonsouth.net
Hey!
> Wouldn’t it be nice to get ‘core-updates-frozen’ merged? :-)
That would be great :) Before merging to master, it would be nice to
have more system tests passing. Currently 16 out of 87 are
broken. Except for the nfs-root-fs that has always been broken, the
other tests probably co
Hello Guix!
Wouldn’t it be nice to get ‘core-updates-frozen’ merged? :-)
What about merging the patches blocked by
<https://issues.guix.gnu.org/50358>? We could even have them on a
separate branch, have Cuirass build it, and merge it 24–36h later, at
which point substitute coverage
On Mon, Sep 27 2021, Mathieu Othacehe wrote:
> Hello,
>
>> The manual should also be updated to reflect this change.
>
> Fixed, thanks for the reminder.
You are welcome! :-)
>> Also, is there any reason for making this change on
>> ‘core-updates-frozen’ rather
Hello,
> The manual should also be updated to reflect this change.
Fixed, thanks for the reminder.
> Also, is there any reason for making this change on
> ‘core-updates-frozen’ rather than ‘master’?
Yes, that's a follow-up of 86cf4c039631cdf15c4c428bf4ffe52d6cbd7d4c that
was pushe
++--
> gnu/tests/databases.scm| 3 +--
> 2 files changed, 3 insertions(+), 4 deletions(-)
The manual should also be updated to reflect this change.
Also, is there any reason for making this change on
‘core-updates-frozen’ rather than ‘master’?
signature.asc
Description: PGP signature
Hello again,
Em quinta-feira, 9 de setembro de 2021, às 19:47:20 -03, Thiago Jung
Bauermann escreveu:
> Hello,
>
> Em quinta-feira, 9 de setembro de 2021, às 19:33:43 -03, Tobias
> Geerinckx-
> Rice escreveu:
> > Thiago Jung Bauermann 写道：
> >
> > > Curiously, the odd-numbered workers still
Hi,
Maxim Cournoyer writes:
> Hello Guix!
>
> Since there's going to be at least this change [0] causing a world
> rebuild of the core-updates-frozen branch, I'd like to know if there are
> other world-rebuilding but low-risk changes you'd like to see integrated
> into the b
change [0] causing a world
> rebuild of the core-updates-frozen branch, I'd like to know if there are
> other world-rebuilding but low-risk changes you'd like to see integrated
> into the branch.
>
> If you do, feel free to 'block' the 50358 issue with the changes, so
> that I ca
Hi Jonathan,
Am Samstag, den 11.09.2021, 00:16 +0200 schrieb Jonathan Brielmaier:
> /gnu/store/2p3lw0dy8b3b34xfn2xlwg9ngrw493v7-gnome-maps-3.38.5.drv
>Fails in testsuite with:
> JS ERROR: Error: Expected 1,001 m (string) but was 1001 m (string)
> I have no clue why, maybe something is
Jonathan Brielmaier skribis:
> Hi Guix folks,
>
> here are the blockers which prevent me from using core-updates-frozen on
> my personal machine. So those 14 derivations failed for me this morning:
>
> [...]
>
> /gnu/store/7mz3ci5gydg606wmh2y6yl7q53mp5x68-materialdecora
Hi Guix folks,
here are the blockers which prevent me from using core-updates-frozen on
my personal machine. So those 14 derivations failed for me this morning:
/gnu/store/fm4wk6zf8zir5qgc7m0fb52i9vrc1a21-gnome-calculator-3.34.1.drv
-> fixed: 67b8aa91f7
/gnu/st
Hello again,
Em quarta-feira, 8 de setembro de 2021, às 12:00:34 -03, Maxim Cournoyer
escreveu:
> Since there's going to be at least this change [0] causing a world
> rebuild of the core-updates-frozen branch, I'd like to know if there are
> other world-rebuilding but low-risk changes y
Hello,
Em quinta-feira, 9 de setembro de 2021, às 19:33:43 -03, Tobias Geerinckx-
Rice escreveu:
> Thiago Jung Bauermann 写道：
>
> > Curiously, the odd-numbered workers still advertise
> > powerpc64-linux:
> > https://ci.guix.gnu.org/machine/hydra-guix-101
>
> …? Curious indeed! I definitely
Thiago Jung Bauermann 写道：
Curiously, the odd-numbered workers still advertise
powerpc64-linux:
https://ci.guix.gnu.org/machine/hydra-guix-101
…? Curious indeed! I definitely remember odd numbers scrolling
by, but I don't recall .101 specifically, nor did I read the
(voluminous) output in
Hello,
Em quinta-feira, 9 de setembro de 2021, às 12:47:56 -03, Tobias Geerinckx-
Rice escreveu:
> Thiago Jung Bauermann 写道：
>
> > Mathieu made the change with commit c0a9022d8234 (“hydra:
> > cuirass: Disable
> > powerpc64le emulation.”) on the maintenance repo (thanks!), so
> > what is left
>
Thiago Jung Bauermann 写道：
Mathieu made the change with commit c0a9022d8234 (“hydra:
cuirass: Disable
powerpc64le emulation.”) on the maintenance repo (thanks!), so
what is left
is deploying it on every hydra build machine for it to take
effect.
I just reconfigured all berlin build nodes,
Hello Maxim,
Em quarta-feira, 8 de setembro de 2021, às 12:00:34 -03, Maxim Cournoyer
escreveu:
> Hello Guix!
>
> Since there's going to be at least this change [0] causing a world
> rebuild of the core-updates-frozen branch, I'd like to know if there are
> other world-rebuildi
Maxim Cournoyer skribis:
> Hello Guix!
>
> Since there's going to be at least this change [0] causing a world
> rebuild of the core-updates-frozen branch, I'd like to know if there are
> other world-rebuilding but low-risk changes you'd like to see integrated
> into the bra
Hello Guix!
Since there's going to be at least this change [0] causing a world
rebuild of the core-updates-frozen branch, I'd like to know if there are
other world-rebuilding but low-risk changes you'd like to see integrated
into the branch.
If you do, feel free to 'block' the 50358 issue
Guillaume Le Vaillant skribis:
> Leo Famulari skribis:
>
>> On Mon, Sep 06, 2021 at 03:39:52PM +, Guillaume Le Vaillant wrote:
>>> There's a bug in binutils 1.37, which we are using on the
>>> core-updates-frozen branch.
>>
>> 2.37, right? :)
>&g
Leo Famulari skribis:
> On Mon, Sep 06, 2021 at 03:39:52PM +, Guillaume Le Vaillant wrote:
>> There's a bug in binutils 1.37, which we are using on the
>> core-updates-frozen branch.
>
> 2.37, right? :)
>
Indeed. :)
>> It's a file descriptor leak that
On Mon, Sep 06, 2021 at 03:39:52PM +, Guillaume Le Vaillant wrote:
> There's a bug in binutils 1.37, which we are using on the
> core-updates-frozen branch.
2.37, right? :)
> It's a file descriptor leak that can lead to 'malformed archive' errors
> when linking libraries. We get
Hi,
There's a bug in binutils 1.37, which we are using on the
core-updates-frozen branch.
It's a file descriptor leak that can lead to 'malformed archive' errors
when linking libraries. We get this problem at least when building
qtwekbit and qtwebengine. A workaround allows us to compile
On Thu, Sep 02, 2021 at 06:47:10PM +0200, Ludovic Courtès wrote:
> Hello!
>
> guix-comm...@gnu.org skribis:
>
> > efraim pushed a commit to branch core-updates-frozen
> > in repository guix.
> >
> > The following commit(s) were added to refs/heads/c
Hello!
guix-comm...@gnu.org skribis:
> efraim pushed a commit to branch core-updates-frozen
> in repository guix.
>
> The following commit(s) were added to refs/heads/core-updates-frozen by this
> push:
> new f883677 gnu: sddm: Fix build.
> f883677 is descr
packages on core-updates-frozen build or not.
Cheers,
simon
Hi,
> From my point of view, yes you can push because it is a fix.
pushed as bac072e09bb80c172672e13782e1ed25ce04d6d5. Please don’t
hesitate to ping me if there’s any other issuse with the sanity check
phase.
Cheers,
Lars
Hi,
On Tue, 31 Aug 2021 at 14:39, Lars-Dominik Braun
wrote:
> See attached patch for a fix.
LGTM.
> Can I simply push that to core-updates-frozen or is there anything else I
> should do?
>From my point of view, yes you can push because it is a fix.
Cheers,
simon
lash.
See attached patch for a fix.
Can I simply push that to core-updates-frozen or is there anything else I
should do?
Lars
--
Lars-Dominik Braun
Wissenschaftlicher Mitarbeiter/Research Associate
www.leibniz-psychology.org
ZPID - Leibniz-Institut für Psychologie /
ZPID - Leibniz
1 - 100 of 139 matches
Mail list logo
