Maxime Devos schreef op di 07-06-2022 om 23:32 [+0200]:
> In my experience with antioxidant, not-up-to-date Rust toolchains do
> not prevent upgrading packages -- in the process of resolving build
> failures, I updated some crates. This never resulted in a ‘you need
> an
> new toolchain error’. A
On 03/06/2022 12:53, jbra...@dismail.de wrote:
I always use this website to remind myself how to use git send-email:
https://git-send-email.io/
We could out that information in the guix manual or link to it. :)
This is great - many thanks for sharing. I think a link in the manual
would be very
On Wed, Jun 8, 2022 at 4:59 PM Ludovic Courtès wrote:
> It looks like ‘cuirass-remote-worker’ needed a kick on these boxes,
> which Mathieu and I did earlier today (‘herd restart …’). Most of them
> are busy right now.
I only count 7 successful builds for aarch64, and several more under
spec:gui
On Mon, Jun 06, 2022 at 11:17:47PM +0200, Ludovic Courtès wrote:
> We have to check for AArch64 & co. Any takers?
>
> Overall it seems to me we should be able to merge ‘staging’ within a
> couple of days. Thoughts?
>
> Ludo’.
>
I mostly succeeded in updating my rock64 aarch64 machine
guix ti
On Thu, Jun 09, 2022 at 07:19:30PM +0200, pelzflorian (Florian Pelz) wrote:
> On Mon, Jun 06, 2022 at 11:17:47PM +0200, Ludovic Courtès wrote:
> > We have to check for AArch64 & co. Any takers?
> >
> > Overall it seems to me we should be able to merge ‘staging’ within a
> > couple of days. Thoug
Hi Giovanni,
>> Guix has very high coding standards
>
> Do you think other software distribution do have less high coding
> standards?
I meant that Guix has very high coding/packaging standards in the
following senses:
- We prefer to not bundle dependencies. Tracking out bundled
dependencies
Hi Ludo,
> I can think of two ways to reassure committers:
>
> 1. By having clear reviewer check lists (you’d do that if you tick all
> the boxes, you’re fine);
>
> 2. By improving automation—nothing new here: if there was a tick that
> says “applies without merge conflicts” and an
On Thu, Jun 09, 2022 at 08:41:21PM +0300, Efraim Flashner wrote:
> I know I've built llvm@11 and mesa on aarch64 hardware for staging.
Oh I see I'm missing the last merge; I'm still at commit b422687cbd.
I will try again with staging at 091eb323ba27. But it will take a
long time; feel free to pr
Hi Guix,
I like the idea of teams. And, it's nice to see so many volunteers raise
their hands!
> * Rust team
> Efraim Flashner
> Aleksandr Vityazev
> Arun Isaac
> John Soo
> Maxim Cournoyer
> Nicolas Goaziou
> Tobias Geerinckx-Rice
However, I know very little about Rust, and I'm not a good fit
Hi Guixers,
What do suggest as a recommended fix for this error?
```
= 482 passed in 3.80s ==
phase `check' succeeded after 5.0 seconds
starting phase `sanity-check'
validating 'flake8'
/gnu/store/zaw5z708sldm6v3qxjczcia7gl65dw5x-python-fla
On Thu, Jun 09, 2022 at 09:02:14PM +0200, pelzflorian (Florian Pelz) wrote:
> I will try again with staging at 091eb323ba27.
llvm@11 was built successfully. Sorry for the noise.
Regards,
Florian
Hi jgart,
> validating 'flake8'
> /gnu/store/zaw5z708sldm6v3qxjczcia7gl65dw5x-python-flake8-3.9.2/lib/python3.9/site-packages
> ...checking requirements: ERROR: flake8==3.9.2
> ContextualVersionConflict(pyflakes 2.4.0
> (/gnu/store/mxkp1zl64cd3i247shp7njkxad8v13x9-python-pyflakes-2.4.0/lib/pyth
12 matches
Mail list logo
