kias...@disroot.org schreef op di 07-06-2022 om 18:39 [+]:
> So without demanding more maintainer time, for now I just convince myself
> that:
> - key toolchains such as Rust and Go are not always up to date, thus blocking
> the
> upgrade of several packages
In my experience with antioxidan
kias...@disroot.org schreef op di 07-06-2022 om 18:39 [+]:
> - we package their dependencies separately (eg Rust crates, Go modules),
> these are a significant portion of Guix that cannot be constantly updated
> easily
> - the Guix 1.4 release is coming soon so more time may be spent debuggin
On 2022-06-04, Ricardo Wurmus wrote:
> As a first step I’d suggest collecting teams, setting up the email
> aliases, and updating the website to show the existing teams. Here’s
> a draft of three teams:
I'm almost afraid to volunteer... but maybe architecture specific teams?
If I were to put my
Hello,
kias...@disroot.org writes:
> I've been watching the Repology page for Guix and I've noticed that
> we've dropped to 51% outdated packages
> [https://repology.org/repository/gnuguix]. We used to be at 40%
> outdated packages a few months ago.
Repology hasn't been able to caught Guix packa
Dear Guix,
I've been watching the Repology page for Guix and I've noticed that we've
dropped to 51% outdated packages [https://repology.org/repository/gnuguix]. We
used to be at 40% outdated packages a few months ago.
I know that rolling release distros don't have to have the latest packages bu
On Sun, Jun 05, 2022 at 11:51:20AM +0200, zimoun wrote:
> Hi Ricardo,
>
>
> > * R team
> > Simon Tournier
> > Ricardo Wurmus
>
> In addition, add me to:
>
> * Julia team
I can do the Julia team too.
--
Efraim Flashner אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D
Hi Ludo'
Sorry for taking a while to send a reply!
On Monday, May 30th, 2022 at 8:33 AM, Ludovic Courtès wrote:
> Hello Kaelyn,
>
> Kaelyn kaelyn.al...@protonmail.com skribis:
>
> > > First, we need to cherry-pick relevant commits from gitlab.com. Any
> > > takers? If you Giovanni or anyone el
Hi,
Vagrant Cascadian skribis:
> But there's one nervous-making issue this revealed; maradns embeds a
> random number at build time ... allegedly for systems that don't have
> /dev/urandom... see
> maradns-3.5.0020/deadwood-3.5.0020/src/Makefile.ubuntu2004:
>
> # Since some systems may not hav
Hi Efraim,
Efraim Flashner skribis:
> As someone who has never used debbugs or emacs I find it daunting to try
> to add it into my workflow. Currently I am subscribed to guix-patches
> and I dump it into my guix-devel mailing list. I read my mail using mutt
> and will just pipe the patches to gi
The upstream website says: "People like MaraDNS because it’s ...
remarkably secure." [1] Since many distributions have the same
issue,
upstream could perhaps offer the patch as a build switch to
enable a
build-time seed only when needed.
Sounds like the safest option. Maybe we could change
On Fri, Jun 03, 2022 at 09:37:36PM +0200, Ludovic Courtès wrote:
> Hi,
>
> Brian Cully skribis:
>
> > Ludovic Courtès writes:
> >
> >> If you are using Emacs, does debbugs.el have
> >> shortcomings that make it a problem to review patches?
>
> To be clear, the question was directed pri
Hi,
On Mon, 06 Jun 2022 at 23:43, Ludovic Courtès wrote:
> 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);
As pointed earlier by Arun in «Public guix offload server» [1], this
check list
12 matches
Mail list logo
