Hi Chris and all,
Christopher Baines skribis:
> I think keeping the Git commit history clean and representative is
> really important, so to me at least this means core-updates can't be
> merged to master in it's current form, even if the changes overall from
> these 6351 commits are
Christopher Baines writes:
> Christopher Baines writes:
>
>> Julien Lepiller writes:
>>
>>> As discussed at Guix Days before Fosdem, we haven't merged core-updates
>>> in a very long time. I'd volunteer to lead this effort, but I don't
>>> know what steps I should follow. Do we have some
Christopher Baines writes:
> Julien Lepiller writes:
>
>> As discussed at Guix Days before Fosdem, we haven't merged core-updates
>> in a very long time. I'd volunteer to lead this effort, but I don't
>> know what steps I should follow. Do we have some documentation about
>> that?
>
> I can
Hi!
Leo Famulari skribis:
> On Sun, Feb 12, 2023 at 10:05:40AM +0100, Julien Lepiller wrote:
>> As discussed at Guix Days before Fosdem, we haven't merged core-updates
>> in a very long time. I'd volunteer to lead this effort, but I don't
>> know what steps I should follow. Do we have some
Hello,
Am Sun, Feb 19, 2023 at 11:24:44PM +0100 schrieb Andreas Enge:
> python-graphviz does not pass its tests any more in core-updates, and
> I can trace it back to your commit 3d388fe3d0475f2e991ae061cc1364529a97af42.
> Adding python-mock back to native-inputs fixes it.
I opted for this fix
Am Sun, Feb 19, 2023 at 12:30:42PM +0100 schrieb Andreas Enge:
> And another one: python-ecdsa
This just built. Strange, but I will not complain!
Andreas
Am Sun, Feb 19, 2023 at 10:59:35PM + schrieb Kaelyn:
> It was mentioned recently that python-pycryptodome is / should be a drop-in
> replacement for python-pycrypto (it is also says that in the package
> description);
Apparently it is not, as Lars wrote. And in any case, it does require
We can probably get rid of most 4.07 variants but I would keep the bootstrap
(in the hope we can bootstrap later versions from it). 4.09 is still used for
unison, and I think Andreas uses it a lot :)
I'd say remove all leaf 4.07 packages that are libraries only.
Le 20 février 2023 11:35:16
Christopher Baines writes:
> [[PGP Signed Part:Undecided]]
>
> Julien Lepiller writes:
>
>> Le Sun, 12 Feb 2023 12:52:51 +0100,
>> Julien Lepiller a écrit :
>>
>>> Le Sun, 12 Feb 2023 12:06:14 +0100,
>>> Andreas Enge a écrit :
>>>
>>> I just tried to build mpc on my machine, from
Hi Julien,
On dim., 19 févr. 2023 at 10:15, Julien Lepiller wrote:
> ocaml-4.14 and ocaml-5 don't have this issue. I just pushed a fix for
> ocaml-4.09. I'll also have to fix ocaml-4.07 since it fails to build as
> early as camlboot. It'll take a while to test. Thanks for pointing me
> to that
--- Original Message ---
On Sunday, February 19th, 2023 at 10:08 PM, Andreas Enge
wrote:
>
> There is poezio, which has a new release (0.14), with a license change to
> gpl3+. I updated python-slixmpp, a dependency of poezio, but this is not
> enough: The newest poezio still depends
Hello Ricardo,
python-graphviz does not pass its tests any more in core-updates, and
I can trace it back to your commit 3d388fe3d0475f2e991ae061cc1364529a97af42.
Adding python-mock back to native-inputs fixes it.
Or maybe python-pytest-mock should have python-mock as propagated input?
It calls
There is poezio, which has a new release (0.14), with a license change to
gpl3+. I updated python-slixmpp, a dependency of poezio, but this is not
enough: The newest poezio still depends on python-potr, which in turn depends
on python-pycrypto.
Andreas
Am Sun, Feb 19, 2023 at 04:50:37PM +0100 schrieb Lars-Dominik Braun:
> The rest seems to be alive
> without any references to python-pycrypto. So these should be upgradable
> and then we can drop python-pycrypto.
I more or less got rid of one of them: python-ledgerblue.
I have updated it from
Am Sun, Feb 19, 2023 at 12:57:07PM +0100 schrieb Andreas Enge:
> > which seems to be the only change in attrdict3, see
> > https://github.com/pirofti/AttrDict3/commit/f6678b627b469c9aeddca2a9e4ba4e1ee9e3ccbb
> Great, I will replace the package then.
Done. Interestingly enough, there was only one
Hi,
> Except that we have to decide what to do about its dependents...
upgrade or drop if not possible. pycryptodome does not provide an entirely
compatible interface (see https://www.pycryptodome.org/src/vs_pycrypto),
so we cannot simply switch existing packages from pycrypto to pycryptdome
> but it is somehow in the same git repository as trezor-agent,
> and I do not totally understand how these are related. Taking
> back my rant and acknowledging my ignorance.
weirdly enough, upstream uses one git repo for multiple projects, and uses
prefixed tag names for them.
FYI, there's
Hello Lars,
thanks for having a look!
Am Sun, Feb 19, 2023 at 12:47:46PM +0100 schrieb Lars-Dominik Braun:
> > command "python" "-m" "compileall" "--invalidation-mode=unchecked-hash"
> > "/gnu/store/5i3yqwaqd8mayl2vr9lmrihxwv8203b1-python-pycrypto-2.6.1" failed
> > with status 1
> this
Am Sun, Feb 19, 2023 at 12:02:15PM +0100 schrieb Andreas Enge:
>Then we have:
> Building the following 6 packages would ensure 9 dependent packages are
> rebuilt: python-miio@0.5.11 ledger-agent@0.9.0 electrum@4.3.2 eolie@0.9.101
> jrnl@1.9.7 poezio@0.13.2
Concerning poezio, it
Hi Andreas,
> *** File
> "/gnu/store/5i3yqwaqd8mayl2vr9lmrihxwv8203b1-python-pycrypto-2.6.1/lib/python3.10/site-packages/Crypto/Util/number.py",
> line 139
> value |= 2L ** (N-1)# Ensure high bit is set
> ^
> SyntaxError: invalid decimal literal
> error: in
And another one: python-ecdsa
I tried to update it from 0.17.0 to 0.18.0, but it still fails its tests
with this message:
src/ecdsa/test_jacobi.py:393: TypeError
=== warnings summary ===
Am Sun, Feb 19, 2023 at 12:15:59PM +0100 schrieb Andreas Enge:
> I am looking at these packages. One of them, ledger-agent, dates from 2017
> and has seen 25 releases in the meantime.
Well, maybe, maybe not. The version in Pypi has not changed,
but it is somehow in the same git repository as
Am Sun, Feb 19, 2023 at 12:02:15PM +0100 schrieb Andreas Enge:
> PPS: On the first issue, the homepage says:
>PyCrypto 2.x is unmaintained, obsolete, and contains security
> vulnerabilities.
> Building the following 6 packages would ensure 9 dependent packages are
> rebuilt:
Hello,
I am having problems with at least two python packages in core-updates:
*** File
"/gnu/store/5i3yqwaqd8mayl2vr9lmrihxwv8203b1-python-pycrypto-2.6.1/lib/python3.10/site-packages/Crypto/Util/number.py",
line 139
value |= 2L ** (N-1)# Ensure high bit is set
ocaml-4.14 and ocaml-5 don't have this issue. I just pushed a fix for
ocaml-4.09. I'll also have to fix ocaml-4.07 since it fails to build as
early as camlboot. It'll take a while to test. Thanks for pointing me
to that patch!
Le Sat, 18 Feb 2023 12:38:55 +0100,
Andreas Enge a écrit :
> Am Sat,
Am Sat, Feb 18, 2023 at 12:03:31PM +0100 schrieb Andreas Enge:
> this looks exactly like the line that posed problems for openjdk.
> Maybe there is a patch? Could someone familiar with ocaml have a look?
It looks like this:
https://github.com/ocaml/ocaml/pull/10266
Andreas
Am Thu, Feb 16, 2023 at 12:38:23PM +0100 schrieb Julien Lepiller:
> Upstream ensures openjdk N+1 can be built by openjdk N, but not necessarily
> with N-1. We can try :)
And fail :)
configure: Potential Boot JDK found at
/gnu/store/lqfppbbxhq503hfy2xf3djivqv3s8df4-openjdk-17.0.5-jdk is
Hello,
Am Mon, Feb 13, 2023 at 09:35:32PM +0100 schrieb Andreas Enge:
> ocaml-4.0.9 fails with
> gcc -c -O2 -fno-strict-aliasing -fwrapv -Wall -fno-tree-vrp -g
> -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DCAML_NAME_SPACE
>
Am Fri, Feb 17, 2023 at 05:27:02PM + schrieb Kaelyn:
> I don't know much about openjdk or its development process, but I had one
> possible thought about the pattern of patch application. Was it a patch that
> was applied or backported to existing openjdk releases, and are @14 and @16
> the
Hi,
--- Original Message ---
On Friday, February 17th, 2023 at 4:28 PM, Andreas Enge wrote:
> Am Fri, Feb 17, 2023 at 03:49:19PM +0100 schrieb Andreas Enge:
>
> > Hm, I compiled up to openjdk@13, @14 fails with the message below.
> > This is strange. It looks as if the patch that has
Julien Lepiller writes:
> Could we get berlin to evaluate a small set of core packages (mpc,
> hello, …)? Are the changes intended to fix the issue with bordeaux's
> machines? Is it configured to build core-updates?
There's some rudimentary support for building packages from branches in
the
Am Fri, Feb 17, 2023 at 03:49:19PM +0100 schrieb Andreas Enge:
> Hm, I compiled up to openjdk@13, @14 fails with the message below.
> This is strange. It looks as if the patch that has become obsolete,
> because integrated into the source @13, is needed again @14!
> And then @15, the patch is
> The following seems to work and create source for openjdk13 and later:
> (define-public openjdk13
> (make-openjdk openjdk12 "13.0.13"
> "0pxf4dlig61k0pg7amg4mi919hzam7nzwckry01avgq1wj8ambji"
> (source (origin
> (inherit (package-source base))
>
Hello,
Am Thu, Feb 16, 2023 at 01:03:35PM +0200 schrieb Efraim Flashner:
> > Okay to push if I manage to build current openjdk with it?
> Yeah, that's probably fine.
after a day, I got past the point of mesa in core-updates on x86_64.
Which in itself is an encouraging milestone.
Andreas
Hi everyone,
I'd love to help with the core-updates merge, but I don't have a beefy
machine right now and would love to avoid building all the bootstrap
locally. The evaluations on CI seem to keep failing, with no info
available [1]. Do we have more info about them/know what's making them
Am Thu, Feb 16, 2023 at 12:41:08PM +0100 schrieb Maxime Devos:
> You didn't write the hash. As the hash is unknown, it would be
> irreproducible for the Guix daemon to grant the build process access to the
> network, so the Guix daemon doesn't.
> You'll need to enter a hash (possibly a bogus one
I haven't tried the patch, but before it, I was already able to build mpc for
x86_64 on a SSD with btrfs.
Le 16 février 2023 16:03:15 GMT+01:00, Janneke Nieuwenhuizen
a écrit :
>Andreas Enge writes:
>
>> Am Wed, Feb 15, 2023 at 09:39:39AM +0100 schrieb Janneke Nieuwenhuizen:
>>> I have
Am Thu, Feb 16, 2023 at 04:03:15PM +0100 schrieb Janneke Nieuwenhuizen:
> Great, thanks so much for checking! Are you using any of tmpfs or btrfs
> on /tmp?
No, it is all on SSD, so we probably cannot conclude for the bugs,
unfortunately.
Andreas
Andreas Enge writes:
> Am Wed, Feb 15, 2023 at 09:39:39AM +0100 schrieb Janneke Nieuwenhuizen:
>> I have released 0.24.2 and updated mes-boot on core-updates as
>> Let's hope this fixes these bugs.
>
> With your latest patch, I have successfully bootstrapped core-updates
> on x86_64 up to hello
Am Wed, Feb 15, 2023 at 09:39:39AM +0100 schrieb Janneke Nieuwenhuizen:
> I have released 0.24.2 and updated mes-boot on core-updates as
> Let's hope this fixes these bugs.
With your latest patch, I have successfully bootstrapped core-updates
on x86_64 up to hello and mpc. Thanks a lot!
Andreas
On 15-02-2023 19:51, Andreas Enge wrote:
I am trying to build openjdk13 without the patch as follows:
(define-public openjdk13
(make-openjdk openjdk12 "13.0.13"
"0pxf4dlig61k0pg7amg4mi919hzam7nzwckry01avgq1wj8ambji"
(source (origin
(method git-fetch)
Le 16 février 2023 12:03:35 GMT+01:00, Efraim Flashner
a écrit :
>On Wed, Feb 15, 2023 at 08:19:08PM +0100, Andreas Enge wrote:
>
>> Is it necessary to keep all these version of openjdk and to bootstrap
>> version n with version n-1?
>
>Probably? I assume if you can cut some out that'd be ok.
On Wed, Feb 15, 2023 at 08:19:08PM +0100, Andreas Enge wrote:
> Am Wed, Feb 15, 2023 at 07:51:56PM +0100 schrieb Andreas Enge:
> > Actually the patch has already been applied to openjdk13, if I am not
> > mistaken. So I do not understand how the source could be built in master
> > then, while the
Am Wed, Feb 15, 2023 at 07:51:56PM +0100 schrieb Andreas Enge:
> Actually the patch has already been applied to openjdk13, if I am not
> mistaken. So I do not understand how the source could be built in master
> then, while the exact same code (?!) fails on core-updates...
Well, there is a
Am Tue, Feb 14, 2023 at 07:27:10PM +0100 schrieb Andreas Enge:
> Am Mon, Feb 13, 2023 at 11:31:15PM +0200 schrieb Efraim Flashner:
> > Looks like you might be able to drop openjdk-10-hotspot-stack-size.patch
> > from openjdk-19.0.1.
> Maybe. What is strange is that we have the same openjdk package
Am Tue, Feb 14, 2023 at 10:10:27PM +0200 schrieb Efraim Flashner:
> > I got to hello on my aarch64, which is very encouraging! I will have to
> > try again with your latest changes to core-updates, but am rather
> > optimistic.
>
> Also I made a typo in the tar fix, so I'll push a fix for that
Andreas Enge writes:
Hello,
> Am Mon, Feb 13, 2023 at 12:34:56PM +0100 schrieb Janneke Nieuwenhuizen:
>> To use stat64 and friends on 32bit, I created the attached patch for GNU
>> Mes and hope to create a 0.24.2 release from
>> https://gitlab.com/janneke/mes/-/tree/wip-stat64
>
> Thanks a
--- Original Message ---
On Tuesday, February 14th, 2023 at 8:29 PM, Kaelyn
wrote:
>
> --- Original Message ---
> On Tuesday, February 14th, 2023 at 2:50 PM, Efraim Flashner
> efr...@flashner.co.il wrote:
>
> [snip]
>
> > I ended up going a different route and moving xz from
--- Original Message ---
On Tuesday, February 14th, 2023 at 2:50 PM, Efraim Flashner
wrote:
>
[snip]
>
> I ended up going a different route and moving xz from the finalize
> packages to an actual xz-final and replacing xz-bootstrap/xz-mesboot in
> %boot6-inputs.
>
> I also tracked
On Tue, Feb 14, 2023 at 05:30:32PM +0100, Andreas Enge wrote:
> Hello,
>
> Am Mon, Feb 13, 2023 at 12:56:45PM +0200 schrieb Efraim Flashner:
> > Aarch64 and armhf are getting stuck at gcc-cross-boot0.
>
> I got to hello on my aarch64, which is very encouraging! I will have to
> try again with
Am Mon, Feb 13, 2023 at 11:31:15PM +0200 schrieb Efraim Flashner:
> Looks like you might be able to drop openjdk-10-hotspot-stack-size.patch
> from openjdk-19.0.1.
Maybe. What is strange is that we have the same openjdk package on master,
apparently with the patch. I will give it a try
Could we get berlin to evaluate a small set of core packages (mpc, hello, …)?
Are the changes intended to fix the issue with bordeaux's machines? Is it
configured to build core-updates?
Le 14 février 2023 17:30:32 GMT+01:00, Andreas Enge a écrit :
>Hello,
>
>Am Mon, Feb 13, 2023 at 12:56:45PM
Hello,
Am Mon, Feb 13, 2023 at 12:56:45PM +0200 schrieb Efraim Flashner:
> Aarch64 and armhf are getting stuck at gcc-cross-boot0.
I got to hello on my aarch64, which is very encouraging! I will have to
try again with your latest changes to core-updates, but am rather optimistic.
Andreas
On Mon, Feb 13, 2023 at 09:36:17PM +, Kaelyn wrote:
> --- Original Message ---
> On Monday, February 13th, 2023 at 8:04 PM, Efraim Flashner
> wrote:
> >
> >
> > On Sun, Feb 12, 2023 at 06:29:04PM +, Kaelyn wrote:
> >
> > > Hi,
> > >
> > > --- Original Message ---
> >
--- Original Message ---
On Monday, February 13th, 2023 at 8:04 PM, Efraim Flashner
wrote:
>
>
> On Sun, Feb 12, 2023 at 06:29:04PM +, Kaelyn wrote:
>
> > Hi,
> >
> > --- Original Message ---
> > On Sunday, February 12th, 2023 at 5:08 PM, Andreas Enge andr...@enge.fr
> >
On Mon, Feb 13, 2023 at 09:35:32PM +0100, Andreas Enge wrote:
> Hello all,
>
> here are my first important failures when trying to go beyond hello and mpc
> (aka the easy C programs):
>
> ocaml-4.0.9 fails with
> gcc -c -O2 -fno-strict-aliasing -fwrapv -Wall -fno-tree-vrp -g
>
Hi
On Mon, Feb 13, 2023 at 12:22 PM Andreas Enge wrote:
>
> It looks like we have reached the Debian trap
How about applying selectively those patches from core-updates that do
not break anything? It would split the difference.
Future changes waiting in Debbugs could join the remainder, which
Hello all,
here are my first important failures when trying to go beyond hello and mpc
(aka the easy C programs):
ocaml-4.0.9 fails with
gcc -c -O2 -fno-strict-aliasing -fwrapv -Wall -fno-tree-vrp -g
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -DCAML_NAME_SPACE
Hello,
Am Sun, Feb 12, 2023 at 05:51:47PM +0200 schrieb Efraim Flashner:
> I think we normally have a 2 week last-chance window to get all sorts of
> last minute packages bumped and then we freeze it and try to build
> "everything".
I am a bit hesitant to let more breakages in :) It looks like
On Sun, Feb 12, 2023 at 06:29:04PM +, Kaelyn wrote:
> Hi,
>
> --- Original Message ---
> On Sunday, February 12th, 2023 at 5:08 PM, Andreas Enge
> wrote:
>
> >
> >
> > Am Sun, Feb 12, 2023 at 12:58:06PM +0100 schrieb Julien Lepiller:
> >
> > > And I was able to rebuild (with
Hi Katherine et al,
On Mon, Feb 13, 2023 at 09:40 AM, Katherine Cox-Buday wrote:
> Efraim Flashner writes:
>
>> On Sun, Feb 12, 2023 at 10:05:40AM +0100, Julien Lepiller wrote:
>>> Hi Guix!
>>>
>>> As discussed at Guix Days before Fosdem, we haven't merged core-updates
>>> in a very long time.
Efraim Flashner writes:
> On Sun, Feb 12, 2023 at 10:05:40AM +0100, Julien Lepiller wrote:
>> Hi Guix!
>>
>> As discussed at Guix Days before Fosdem, we haven't merged core-updates
>> in a very long time. I'd volunteer to lead this effort, but I don't
>> know what steps I should follow. Do we
Am Mon, Feb 13, 2023 at 12:34:56PM +0100 schrieb Janneke Nieuwenhuizen:
> To use stat64 and friends on 32bit, I created the attached patch for GNU
> Mes and hope to create a 0.24.2 release from
> https://gitlab.com/janneke/mes/-/tree/wip-stat64
Thanks a lot, Janneke!
> Just hoping this is
Andreas Enge writes:
> Am Sun, Feb 12, 2023 at 12:58:06PM +0100 schrieb Julien Lepiller:
>> And I was able to rebuild (with --check) patch-mesboot. The error looks
>> a lot like https://issues.guix.gnu.org/49985. We should fix that indeed
>> :)
>
> Ah indeed, that looks like deal breaking; maybe
On Mon, Feb 13, 2023 at 10:43:17AM +0100, zimoun wrote:
> Hi,
>
> Well, it could be helpful is Berlin or Bordeaux could build some
> manifest of core-updates (not necessary the whole core-updates). And
> then, once the manifest builds, we could add some packages and repeat.
>
> It would avoid
Hi,
On Sun, 12 Feb 2023 at 10:05, Julien Lepiller wrote:
> As discussed at Guix Days before Fosdem, we haven't merged core-updates
> in a very long time. I'd volunteer to lead this effort, but I don't
> know what steps I should follow. Do we have some documentation about
> that?
Maybe a start
Hi guix-devel!
On Sun, Feb 12, 2023 at 03:49 PM, Josselin Poiret wrote:
> Hi everyone,
>
> Andreas Enge writes:
>
>> I volunteer to follow your lead, but also have no clue what is actually
>> expected.
>
> I would also like to give a hand!
>
Count me in as well!
I only did some spot fixes the
Andreas Enge writes:
> Am Sun, Feb 12, 2023 at 12:58:06PM +0100 schrieb Julien Lepiller:
>> And I was able to rebuild (with --check) patch-mesboot. The error looks
>> a lot like https://issues.guix.gnu.org/49985. We should fix that indeed
>> :)
>
> Ah indeed, that looks like deal breaking; maybe
Hi,
--- Original Message ---
On Sunday, February 12th, 2023 at 5:08 PM, Andreas Enge wrote:
>
>
> Am Sun, Feb 12, 2023 at 12:58:06PM +0100 schrieb Julien Lepiller:
>
> > And I was able to rebuild (with --check) patch-mesboot. The error looks
> > a lot like
Am Sun, Feb 12, 2023 at 12:58:06PM +0100 schrieb Julien Lepiller:
> And I was able to rebuild (with --check) patch-mesboot. The error looks
> a lot like https://issues.guix.gnu.org/49985. We should fix that indeed
> :)
Ah indeed, that looks like deal breaking; maybe someone from MES can have
a
On Sun, Feb 12, 2023 at 10:05:40AM +0100, Julien Lepiller wrote:
> Hi Guix!
>
> As discussed at Guix Days before Fosdem, we haven't merged core-updates
> in a very long time. I'd volunteer to lead this effort, but I don't
> know what steps I should follow. Do we have some documentation about
>
Hi everyone,
Andreas Enge writes:
> I volunteer to follow your lead, but also have no clue what is actually
> expected.
I would also like to give a hand!
> [...]
> Actually I am wondering whether the first step of killing these untamed
> non-feature branches would not be to build and merge
Julien Lepiller writes:
> As discussed at Guix Days before Fosdem, we haven't merged core-updates
> in a very long time. I'd volunteer to lead this effort, but I don't
> know what steps I should follow. Do we have some documentation about
> that?
I can try and help with this, at least in terms
Julien Lepiller writes:
> Le Sun, 12 Feb 2023 12:52:51 +0100,
> Julien Lepiller a écrit :
>
>> Le Sun, 12 Feb 2023 12:06:14 +0100,
>> Andreas Enge a écrit :
>>
>> I just tried to build mpc on my machine, from core-updates. I get the
>> same derivation as the one shown on the data service,
On Sun, Feb 12, 2023 at 10:05:40AM +0100, Julien Lepiller wrote:
> As discussed at Guix Days before Fosdem, we haven't merged core-updates
> in a very long time. I'd volunteer to lead this effort, but I don't
> know what steps I should follow. Do we have some documentation about
> that?
The
Le Sun, 12 Feb 2023 12:52:51 +0100,
Julien Lepiller a écrit :
> Le Sun, 12 Feb 2023 12:06:14 +0100,
> Andreas Enge a écrit :
>
> I just tried to build mpc on my machine, from core-updates. I get the
> same derivation as the one shown on the data service, and it built
> fine. Maybe there's
Le Sun, 12 Feb 2023 12:06:14 +0100,
Andreas Enge a écrit :
> Hello,
>
> Am Sun, Feb 12, 2023 at 10:05:40AM +0100 schrieb Julien Lepiller:
> > As discussed at Guix Days before Fosdem, we haven't merged
> > core-updates in a very long time. I'd volunteer to lead this
> > effort, but I don't know
Hello,
Am Sun, Feb 12, 2023 at 10:05:40AM +0100 schrieb Julien Lepiller:
> As discussed at Guix Days before Fosdem, we haven't merged core-updates
> in a very long time. I'd volunteer to lead this effort, but I don't
> know what steps I should follow. Do we have some documentation about
> that?
Hi Guix!
As discussed at Guix Days before Fosdem, we haven't merged core-updates
in a very long time. I'd volunteer to lead this effort, but I don't
know what steps I should follow. Do we have some documentation about
that?
Hi Ludo,
> ‘core-updates’ is now merged!
Yay!
> Now the question is whether we can merge ‘wip-gnome-upgrades’ before the
> release, which I’d like to push out later this week, or whether it
> should wait a few more days.
Unfortunately, gnome-shell segfaults on wip-gnome-upgrades. I’ve
Hello Guix!
‘core-updates’ is now merged!
Thanks to everyone who contributed to the tedious testing and
stabilization process. It certainly took us way too long but now we’re
happy to get all the new stuff: glibc 2.28, guile 2.2.4 by default, and
lots of things we worked on so long ago that we
Hi Danny,
Danny Milosavljevic skribis:
> On Sat, 01 Dec 2018 19:20:26 +0100
> l...@gnu.org (Ludovic Courtès) wrote:
>
>> On x86_64, LibreOffice, IceCat, etc. are available as substitutes; ‘guix
>> weather’ reports only 50% of coverage on berlin and 80% on
>> mirror.hydra.gnu.org (we’ll have to
Hi Ludo,
On Sat, 01 Dec 2018 19:20:26 +0100
l...@gnu.org (Ludovic Courtès) wrote:
> On x86_64, LibreOffice, IceCat, etc. are available as substitutes; ‘guix
> weather’ reports only 50% of coverage on berlin and 80% on
> mirror.hydra.gnu.org (we’ll have to elucidate the bad number on berlin.)
>
Ricardo Wurmus writes:
>> Overall I’m in favor of merging.
>
> I agree.
>
> I’ve been using core-updates on my laptop (both system and user profile)
> for about a week now without any problems.
Me too.
janneke
Hi,
> ‘core-updates’ seems to be in a rather good shape. […]
> On x86_64, LibreOffice, IceCat, etc. are available as substitutes; ‘guix
> weather’ reports only 50% of coverage on berlin and 80% on
> mirror.hydra.gnu.org (we’ll have to elucidate the bad number on berlin.)
> I’m using
Hello Guix!
‘core-updates’ seems to be in a rather good shape. Unfortunately, the
web UI and APIs of hydra.gnu.org and berlin.guixsd.org make it difficult
to have a clear view of the situation.
“make assert-binaries-available” passes for all architectures, meaning
we have Emacs/X11 among other
86 matches
Mail list logo
