Re: wishlist: “repack” generations history of profile

Hi, On Sat, 04 Jun 2022 at 09:39, Giovanni Biscuolo wrote: > IMHO all users must understand that for > their projects (profiles) to be reproducible and versioned the /only/ > way is to keep channels.scm and manifests.scm in a VCS (i.e. git) I agree. This pract

Re: Teams

Hi Ricardo, On Sat, 04 Jun 2022 at 14:07, 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: Well, a team per build system would fit more or less the needs,

Re: Mummi wishlist: API using Message-ID

Hi Ricardo, On Sat, 04 Jun 2022 at 13:00, Ricardo Wurmus wrote: > This is now implemented in mumi. Really cool! Thank you! The bridge between tools becomes easier. For instance, I use the Emacs frontend of Notmuch where ’cI’ allow to stash the Message-ID, then I can directly paste it for ref

Re: Release v1.4?

Hi, On Fri, 03 Jun 2022 at 18:41, Ludovic Courtès wrote: > guix time-machine --branch=staging -- … > > Remaining things to check: > > - [ ] system tests > - [ ] status on non-x86_64 architectures I agree. To me, it is part of the same effort. From my point of view, we missed the window

Re: On commit access, patch review, and remaining healthy

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

«Reproducibility vs. Replicability: A Brief History of a Confused Terminology»

Hi, On Sun, 12 Jun 2022 at 15:10, Maxime Devos wrote: > It's ‘reproducible’ in the trivial sense that you can ‘reproduce’ a > scientific paper by putting it a photocopier. That way, you can > reproduce the results, but you cannot confirm whether these results > were correct. More details for t

Release ? (was: Merging ‘staging’?)

Hi, On Mon, 13 Jun 2022 at 09:03, Ludovic Courtès wrote: > Merged, enjoy! :-) Cool! > Next up: release and ‘core-updates’. Do you want to do a ’core-updates’ merge before the release? I think a release on July would be very welcome. WDYT? Cheers, simon

Re: On commit access, patch review, and remaining healthy

Hi, On Sat, 11 Jun 2022 at 01:13, Thiago Jung Bauermann wrote: > But I do think it's one more source of “friction” for new contributors, > and one more thing for us to require that they get right. [...] > There's one in the GNU Coding Standards¹: [...] > Personally, I think nowadays this pu

Re: On commit access, patch review, and remaining healthy

Hi, On Wed, 08 Jun 2022 at 11:30, Giovanni Biscuolo wrote: >> It reduces a bit the pressure on the committers, IMHO. > > It raises a bit the pressure on the maintainers, IMHO :-) What does it mean “maintainer” here? Maybe I miss something but I do not think the Guix maintainers play a special

Re: FSDG-compatibility of APSL-2.0

Hi, On Thu, 16 Jun 2022 at 18:02, Philip McGrath wrote: > I don't want to speak for Maxime, but AIUI the question was whether Guix > ought > to continue to accept all licenses on that list, or instead ought adopt some > different (more stringent?) license policy. FWIW, I think that adopting

Re: PARI/GP and parallelism

Hi Andreas, On Fri, 17 Jun 2022 at 14:35, Andreas Enge wrote: > configure flag "--mp=pthread". It will transparently parallelise a number ^ --mt=pthread > What do you think? Are there any objections? No objection. Maybe it is the occasion to also transf

Re: FSDG-compatibility of APSL-2.0

tion is about dependencies and linking because APSL is incompatible with the GPL. If all is fine, then let include ’cctools’ in Guix. 1: <https://www.gnu.org/licenses/license-list.html> 2: <https://issues.guix.gnu.org/55998> On Fri, 17 Jun 2022 at 11:40, Maxime Devos wrote:

sssd, not nscd, foreign distro and release?

Hi, On Tue, 01 Mar 2022 at 18:24, Ludovic Courtès wrote: > Ludovic Courtès skribis: >> Chris Marusich skribis: >> >>> The Guix manual recommends running nscd: >>> >>> https://guix.gnu.org/manual/en/html_node/Application-Setup.html >>> >>> However, Fedora intends to remove it: >>> >>> https://fe

Teams: first draft list

Hi, On Sat, 04 Jun 2022 at 14:07, 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: Here below a collection of answers. The teams are more or less. Maybe,

Re: On commit access, patch review, and remaining healthy

Hi Hartmut, On Mon, 20 Jun 2022 at 14:53, Hartmut Goebel wrote: > my system is set up to emacs could send out mails. Well, if you are already using Emacs, the Emacs front-end is not the nicest interface but does part of the job. I have this: --8<---cut here--

Re: Teams: first draft list

On Tuesday, 21 June 2022, wrote: > On +2022-06-21 17:21:11 +0200, zimoun wrote: > > > > Here below a collection of answers. The teams are more or less. Maybe, > > we could join some for having another structure. WDYT? > > Where is the RISC/MES team? :) > Embeded / Bootstrap ;-)

Re: Teams: first draft list

Hi Ricardo, On Wed, 22 Jun 2022 at 09:59, Ricardo Wurmus wrote: > I also wonder about how / if we should notify teams about relevant > patches. Will contributors Cc the relevant teams or will we have team > predicates, e.g. a procedure that spits out the appropriate teams when > given a patch?

Re: proposal: guix-ment...@gnu.org list/alias

Hi, What is the status of this initiative? On Wed, 01 Jun 2022 at 22:17, Ricardo Wurmus wrote: > to help new contributors get their first contribution into Guix I think > it would be good to do this: > > 1. create a new private mailing list or mailing alias guix-ment...@gnu.org > > 2. ask for e

Re: proposal: guix-ment...@gnu.org list/alias

Hi, On Wed, 22 Jun 2022 at 11:44, Ricardo Wurmus wrote: > Only two people have come forward as possible mentors (Ludo and I). > With only two potential mentors there’s no point in doing this as it’s > not sustainable. Add me as possible mentor. Well, I do not know if I am enough qualified for

Seek Gitolite users (was bug#25957: gitolite broken: created repositories keep references to /usr/bin for hooks)

Hi, This old bug #25957 [1] needs a Gitolite user. :-) 1: On Mon, 28 Mar 2022 at 09:49, Efraim Flashner wrote: > I spent some time looking at gitolite and the service. As I understand > it, with the exception of svnserve, it searches $PATH for a number

Unreproducible «When Docker images become fixed-point»?

Hi, Preparing a session about Guix, I was checking this blog post: https://hpc.guix.info/blog/2021/10/when-docker-images-become-fixed-point/ explaining how to rebuild a Docker pack using a Docker pack produced by Guix itself. It is from Oct. 2021. The pack built by the post is: /gnu/stor

Re: Dealing with upstream issues

Hi Maxime, On Mon, 27 Jun 2022 at 12:37, Maxime Devos wrote: > Also, some of those rules are incorrect -- "guix style" occasionally > makes things wrong and patch submitters had to be told to not follow > it. Do you have concrete examples in mind? Cheers, simon

Re: Dealing with upstream issues

Hi, Well, from my understanding, there is mismatches between “review process”, “adoption in Guix” and “fix upstream”. On Mon, 27 Jun 2022 at 12:10, Ludovic Courtès wrote: >> AFAICT the issues have not been reported upstream yet, so I don't think >> we can close this entry on debbugs yet. Whil

Re: Dealing with upstream issues

On Mon, 27 Jun 2022 at 16:20, Maxime Devos wrote: > E.g.: https://issues.guix.gnu.org/55606#16 Do you mean --8<---cut here---start->8--- > +(define-public harec > + (let ((commit "bbabe09bddf74bd699f8ad2224fdd6e2eefbd35e") > (revision "0")) Despite what (gui

Re: Dealing with upstream issues

Hi, On Mon, 27 Jun 2022 at 16:32, Maxime Devos wrote: >> Maybe I misunderstand the point.  To me, the aim of the package >> submission is the inclusion in Guix.  AFAIK, the Guix project is not >> applying any standard audit on the upstream code before inclusion. >> >> Therefore, if the upstream

Re: Dealing with upstream issues

ot currently being entered. > * https://issues.guix.gnu.org/44199 (it's a WIP, not completed yet, but still > closed!) This history is: Maxime Devoswrote on 24 Oct 2020 21:47 zimoun wrote on 27 Oct 2020 14:39 Maxime Devoswrote on 27 Oct 2020 19:50 Maxime Devoswrote on 1 Nov 202

Re: First guix pull is too costly

Hi, On Tue, 28 Jun 2022 at 14:04, Akib Azmain Turja wrote: > Is possible to reuse the guix channel from any other user to do the > first guix pull? Or maybe a shallow clone? Assuming alice is user already existing on the machine and bob is the new user. Something like should do the job, --8<

Re: Dealing with upstream issues

Hi, On Tue, 28 Jun 2022 at 14:21, Maxime Devos wrote: > zimoun schreef op di 28-06-2022 om 13:01 [+0200]: >> Well, from my understanding, the question is: should a perfectly working >> and fine submission be delayed because unrelated-to-Guix issues are in >> upstream code

Re: Dealing with upstream issues

Hi, On Tue, 28 Jun 2022 at 14:31, Maxime Devos wrote: > You often close bugs with as rationale: ‘no response since X months, > hence closing’, so it seems to me that you would simply close bug > reports if the bug reporter is gone. [...] > That's the issue I wanted to highlight -- issues are c

Re: First guix pull is too costly

Hi Efraim, On Tue, 28 Jun 2022 at 15:28, Efraim Flashner wrote: > There's already a copy of the guix source code at > /run/current-system/profile/share/guile/site/3.0/guix, what if we "just" > switched the new-user/new-cache experience to: This is only for Guix System and not on foreign distro,

Re: First guix pull is too costly

Hi, On Tue, 28 Jun 2022 at 18:49, Akib Azmain Turja wrote: > Just out of curiosity, why the hash is > pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq? Is this the hash > of the channel declaration/definition/whatsoever? --8<---cut here---start->8--- $ g

Re: Dealing with upstream issues

Hi, On Tue, 28 Jun 2022 at 18:47, Maxime Devos wrote: > It is -- where's the bug report upstream or a fix? Upstream [1] does not have a bug tracker, or I am missing it. See bug#56285 for tracking the issue in Guix. 1: 2:

Missing tags in Debbugs?

Hi, Thanks for the feed back On Wed, 29 Jun 2022 at 08:07, b...@bokr.com wrote: > Anyway, the idea is to make the Subject: line greppable for both > what the bug is about and its status when it was closed. I agree that it is hard to work with the Debbugs archive. What you are asking seems poss

Re: Non-free data in Poppler test suite

Hi Marius, On Tue, 28 Jun 2022 at 23:19, Marius Bakke wrote: > I discovered a potential freedom issue with the Poppler test suite. > Specifically it includes a file with the CC BY-NC-ND (non-commercial) > license: BY-NC-ND in short: This license allows reusers to copy and distribute th

Re: First guix pull is too costly

Hi, On ven., 01 juil. 2022 at 14:51, Ludovic Courtès wrote: > I was thinking we could have a “Git checkout cache daemon”, so that > things currently in ~/.cache/guix/checkouts could somehow be shared > safely among users. Yeah, maybe Git worktree could be used. Aide the optimization of the fir

Re: Can't install wine, curl build fails at 'check' stage

Hi, What is your arch? On x86-64, it works for me. On ven., 01 juil. 2022 at 22:33, Akib Azmain Turja wrote: > TESTFAIL: These test cases failed: 3026 > > make: *** [Makefile:809: test] Error 1 > make: Leaving directory '/tmp/guix-build-curl-7.84.0.drv-0/curl-7.84.0/tests' > error: in phase

Re: “Building a Secure Software Supply Chain with GNU Guix”

Hi Bengt, On jeu., 30 juin 2022 at 23:37, b...@bokr.com wrote: > I think IWBN to have some kind of trust code come with that git output, > like gpg's 1-5 but indicating how well the committer/signer trusts > that using the code will *not* cause a problem. Well, from my understanding, Guix is dea

Re: “Building a Secure Software Supply Chain with GNU Guix”

Hi, On Sun, 03 Jul 2022 at 12:38, Bengt Richter wrote: >> I do not think committers are pushing code about #1, #2 or #3 that they >> know beforehand it will cause a problem. > > Hm, -- unless ... ? :) > I do not understand what you mean? >> The GPG trust level works because it is based on the

Re: repl macro (metacommand?) for guix CLI (sub)commands

Hi, On Sun, 03 Jul 2022 at 13:11, jgart wrote: > What do guixers think of having a repl macro that allows > you to run commands like if you were using the CLI? I am not sure to understand the question. Well, it is already possible, no? --8<---cut here---start---

Re: Can't install wine, curl build fails at 'check' stage

Hi, On Sat, 02 Jul 2022 at 10:18, Akib Azmain Turja wrote: > I don't know why this is occurring. "guix install curl" installs curl > 7.79.1, but "guix install wine" tries to install curl 7.84.0, and fails. I do not know why it fails for you. The substitute is available: https://ci.guix.g

Re: Why do Emacs packages still pull emacs-transient?

Hi, On Sun, 03 Jul 2022 at 19:10, "Jorge P. de Morais Neto" wrote: > So, why do many Emacs packages still pull emacs-transient, when Guix has > Emacs version 28.1, which has Transient built-in? This redundancy > wastes (a little bit of) bandwidth, install time and disk space, and, > worse, cau

Re: Shall updaters fall back to other updaters?

Hi, On Thu, 30 Jun 2022 at 10:58, Hartmut Goebel wrote: > BTW 2: Which updater is used for each package is non-deterministic. >From (guix discovery), ’all-modules’ is not deterministic because it depends on how the filesystem tree is walked. Therefore, indeed ’importer-modules’ from (guix ups

Re: guix refresh to a specific version?

Hi, Thanks for working on this. On Mon, 04 Jul 2022 at 16:06, Hartmut Goebel wrote: > ?bioconductor (cran.scm) -- repo supports latest version only It is indeed a limitation of the Bioconductor importer and the issue is discussed here: http://issues.guix.gnu.org/issue/39885 http://i

Re: Can't install wine, curl build fails at 'check' stage

Hi, On Mon, 04 Jul 2022 at 15:40, Ludovic Courtès wrote: > Indeed, ‘guix build > /gnu/store/v3kc0z1mx7zai6hky8kzlp171cxr2ccj-curl-7.84.0.drv’ fails with: [...] > Now, I don’t see where this .drv comes from. Here’s what I see on > x86_64: I think it comes from a twist with i686: --8<

’guix package --export-manifest’ using ’@version’?

Hi, I have not noticed at the time when discussing ’export-manifest’. Sorry to have overlooked that. Because of #:entry-package-version, --8<---cut here---start->8--- (match (manifest->code manifest #:entry-package-version

Re: repl macro (metacommand?) for guix CLI (sub)commands

Hi, >>This is because each of those "CLI calls" end up running `(exit 0)` >>at the end in some form or another. Quote: What do guixers think of having a repl macro that allows you to run commands like if you were using the CLI?

Re: Unreproducible «When Docker images become fixed-point»?

Hi, On Mon, 04 Jul 2022 at 15:37, Ludovic Courtès wrote: > Do you still have the original tarball mentioned in the post? Sadly no. > A possible reason why we’re building a different derivation than back > then is provenance info: as explained under ‘--save-provenance’ in the > manual, provena

grafted package and CLI

Hi, Commit 3fc6709d4285f44d1e861c7b09951adf3073e898 is a security fixes for the package ’curl’; it reads, --8<---cut here---start->8--- (define-public curl (package (name "curl") (version "7.79.1") + (replacement curl-7.84.0) [...] +;; Replacemen

Re: guix refresh to a specific version?

Hi, On Tue, 5 Jul 2022 at 11:32, wrote: > Just wondering if you are posting these as "http" links for some > hidden reason :) Because my Emacs helper [1] still uses 'http'. 1: <https://gitlab.com/zimoun/my-conf/-/blob/master/.config/emacs/lisp/funs.el#L271-297> Cheers, simon

Re: Unreproducible «When Docker images become fixed-point»?

Hi, On Tue, 05 Jul 2022 at 09:44, Ludovic Courtès wrote: > (define-public %localstatedir "/var") This one is for sure the same. > (define-public %sysconfdir "/etc") I do not remember. However, I am aware of such potential issue since I sent this patch [1] because I already hit non-reprod

Re: repl macro (metacommand?) for guix CLI (sub)commands

Hi, On mar., 05 juil. 2022 at 17:27, jgart wrote: > That's a good question! Maybe we should make a feature table and analyze > what we currently have exposed to decide what we might want in the near > future that we don't currently have. What is already exposed: --8<---cut here

Julia packages on build farms?

Hi, I am confused by the missing Julia substitutes on Berlin (ci.guix). And I miss why the are missing – another topic; what recently changed on master that could trigger this rebuild? That’s said, I do not understand the result of “guix weather” and “guix build”. Let pick an example. Using Gu

Re: Julia packages on build farms?

Hi, On mer., 06 juil. 2022 at 12:41, Christopher Baines wrote: >> What am I doing wrong? > > guix weather doesn't check substitute trust, so you've probably not got > the bordeaux.guix.gnu.org key in your ACL. Indeed. Thanks. I thought it was done by default when answering yes to the question

Re: Julia packages on build farms?

Hi, On mer., 06 juil. 2022 at 14:33, Efraim Flashner wrote: > I added a patch to tbb on 4 July to add support for riscv64 (and maybe > other architectures) and that caused a rebuild of julia. I have since > rebuilt all the julia packages locally. I did find that sometimes while > building all th

Re: ’guix package --export-manifest’ using ’@version’?

Hi, On Thu, 07 Jul 2022 at 09:57, Ludovic Courtès wrote: > (Nitpick: it *is* stateless, in the sense that it only depends on Guix > itself, not on the state of the machine where it is being run.) I will not argue about what we call state here. :-) > ‘--export-manifest’ emits a comment (shown

Re: grafted package and CLI

Hi, On Thu, 07 Jul 2022 at 10:00, Ludovic Courtès wrote: > Usually, when the replacement is a different version, we make it public, > so it also shows up in ‘guix package -A’. It’s just a convention, but > it’s probably good enough? About “guix package -A”, we cannot do more, so let say it is

Re: grafted package and CLI

Hi, On Thu, 07 Jul 2022 at 17:09, Ludovic Courtès wrote: > You mean hide with the ‘hidden?’ property? I do not know what I mean. ;-) The replacement could have an ’hidden?’ property or not being ’define-public’. > Good question. There’s probably little point in exposing the original > (rep

Re: ’guix package --export-manifest’ using ’@version’?

Hi, On Thu, 07 Jul 2022 at 17:13, Ludovic Courtès wrote: > The “@X.Y” bit is added only when necessary to disambiguate the package > spec. So with today’s Guix, we have: Yes, but it is not what I reported initially [1]; it was: 1: https://yhetil.org/guix/868rp8zosc@gmail.com --8<

Re: repl macro (metacommand?) for guix CLI (sub)commands

Hi, On mer., 06 juil. 2022 at 14:13, b...@bokr.com wrote: > [13:23 ~/bs]$ guile --no-auto-compile -c '(display (getenv "PS1"))(newline)' > [\A \w]\$ On my machine, all is as usual and I run Bash: --8<---cut here---start->8--- $ echo $PS1 \n\w/\n\u@\h$ $ guil

Re: Shall updaters fall back to other updaters?

Hi, On mer., 06 juil. 2022 at 16:16, Ludovic Courtès wrote: > Nope! ‘all-modules’ *is* deterministic because it builds upon > ‘scheme-files’, which is deterministic and documented as such. Oh indeed! My bad, I have overlooked that ’scheme-files’ uses ’scandir*’ instead of Guile scandir; and t

Re: Error when compiling file using Bigloo Scheme

Hi, On jeu., 07 juil. 2022 at 15:56, Sam Lee wrote: > $ bigloo myfile.scm > /usr/bin/ld: cannot find -lunistring > collect2: error: ld returned 1 exit status Indeed, bigloo requires some packages. This works for me: --8<---cut here---start->8---

Re: Error when compiling file using Bigloo Scheme

On Fri, 08 Jul 2022 at 18:53, Liliana Marie Prikler wrote: > We don't typically propagate packages, especially not gcc-toolchain. > You should be able to swap that out for any other toolchain, e.g. > another version of gcc-toolchain or perhaps even clang-toolchain. I'm > not sure about libun

Re: emacs-flymake-guix `guix lint -n`

Hi, On Wed, 13 Jul 2022 at 21:18, jgart wrote: > Hi Guixers is there currently an emacs package that provides a flymake > backend for `guix lint -n`? What do you mean? Well, the Emacs package emacs-guix allows to use “guix lint” from Emacs. Maybe improving this emacs-guix could be worth. Or

Re: [WIP Patch] Adding an FHS container to guix shell

Hi On Tue, 12 Jul 2022 at 15:59, John Kehayias wrote: > Apologies for the long email, so let me start with the punchline: > attached is a diff which adds an '--fhs-container' (or -F) option to > guix shell/environment to set up an FHS-like container. This includes > the usual /lib directory and

Re: Could Guix System eventually run on top of HyperbolaBSD ? slightly off topic

Hi, On Mon, 11 Jul 2022 at 18:44, Joshua Branson wrote: > The Hyperbola GNU/Linux team recently announced that they would ditch > Linux for OpenBSD. They are using the OpenBSD kernel and the OpenBSD > userland. And they are GPL-ing all of the code. It sounds like they will > have to replace 20%

Re: Could Guix System eventually run on top of HyperbolaBSD ? slightly off topic

Hi Tobias, All, (French Bastille Day is a day off, so a day for trolling. ;-)) On Thu, 14 Jul 2022 at 10:40, Tobias Geerinckx-Rice wrote: > https://www.hyperbola.info/news/announcing-hyperbolabsd-roadmap/ Thanks for the link. It is helpful for understanding. :-) > Far from 'recent' in my b

Re: Could Guix System eventually run on top of HyperbolaBSD ? slightly off topic

Hi Raghav, On Wed, 20 Jul 2022 at 12:03, Raghav Gururajan wrote: > [1] The idea isn't off-topic, because, Guix is meant to be kernel > agnostic. So exploring HyperbolaBSD as a kernel option for Guix is with > in the prospect. Hum, I do not think that Guix is agnostic about the standard C lib

Re: native-inputs: Go for completeness or minimalism?

Hi Hartmut, On Wed, 20 Jul 2022 at 10:33, Hartmut Goebel wrote: > Personally I tend to minimal. Me too. Being minimal is better on all aspects, IMHO. The only drawback is indeed “guix shell -D”. But, people developing can add the missing or extra packages. To me, Guix provides the minimal

Re: debbugs irritation Was: [WIP Patch] Adding an FHS container to guix shell

Hi, On Thu, 21 Jul 2022 at 02:20, Csepp wrote: > I was looking for this patch on issues.guix.gnu.org and could not figure > out why it's not there and I'd just like to point out that having like 6 > mailing lists with at least two separate indexes is... not great :) I > appreciate everyone's work

Re: Enabling tracing on a phase to debug?

Hi Maxim, On Fri, 15 Jul 2022 at 15:53, Maxim Cournoyer wrote: > I was toying with the idea to programatically enable tracing the > execution of a single build phase to aid with debugging, and came up > with this with the help of robin on #guix (thanks!) Well, I am often annoyed when debugging

Re: GitLab to plans to delete dormant projects

Hi, I guess, Gitlab means the instance gitlab.com, right? On sam., 06 août 2022 at 09:08, Olivier Dion via "Development of GNU Guix and the GNU System distribution." wrote: > Many packages origin in Guix use an url to a GitLab project. What are > the consequence of such deletion on Guix repr

Re: debbugs irritation Was: [WIP Patch] Adding an FHS container to guix shell

tom function [1] “M-x my/guix-issues“ which adds to the kill-ring an URL. Recently, Ricardo added Message-ID to Mumi which helps too; using emacs-notmuch, just "ci” for stashing and then pasting elsewhere. 1: <https://gitlab.com/zimoun/my-conf/-/blob/master/.config/emacs/lisp/funs.

Re: Building, packaging and updating Guix with confidence

Hi Josselin, Thank you for the clear explanations. On mer., 06 juil. 2022 at 22:01, Josselin Poiret wrote: [...] > What I personally think, is that we should rationalize the way we > interact with Guix source: a running Guix should always be able to hold > a reference to its source. The guix

Re: Building, packaging and updating Guix with confidence

Hi Bengt, On mar., 26 juil. 2022 at 03:09, Bengt Richter wrote: > I naively don't buy the rationale against a non-root guix daemon :) For sure, we can imagine many other designs than the current implemented one. However, at one point or the other, “something with privileges” is required, no?

Re: A real-life test of long-term reproducibility

Hi Blake, I am late to the party. :-) On jeu., 04 août 2022 at 15:35, bl...@reproduciblemedia.com wrote: > August 4, 2022 8:43 AM, "Konrad Hinsen" wrote: >> One of our claims is that Guix can rebuild code identically as long as >> we have a machine with a Linux kernel and a POSIX filesystem. T

Re: A real-life test of long-term reproducibility

Hi Konrad, On lun., 08 août 2022 at 10:44, Konrad Hinsen wrote: >> Besides, I recently added ‘etc/time-travel-manifest.scm’ and added a >> corresponding jobset at > > Nice! Guix will be certified for time travel! [...] >> For best practices, I do h

Cabal mismatch in ghc-lucid; long-term archiving Haskell?

Hi, Let try to build the Haskell package ghc-lucid. --8<---cut here---start->8--- $ guix build ghc-lucid substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0% The following derivations will be built: /gnu/store/9m71fs1i0anv89f5zq44hbh2wn2l

Failure with “guix copy“

Hi, Using Guix 65cabb0, I do not understand why ‘guix copy’ fails. Well, I have some items in the store of my remote desktop machine. --8<---cut here---start->8--- $ ssh desktop -t guix build hledger ghc-lucid /gnu/store/f23gh2padz9xwsjgz5znfk9azn5l101z-ghc-l

Re: Cabal mismatch in ghc-lucid; long-term archiving Haskell?

Hi Lars, On sam., 20 août 2022 at 18:47, Lars-Dominik Braun wrote: >> In all cases, these revised Cabal files are not archived elsewhere than >> in Hackage, right? The question is thus, where could we archive them? > And while I updated the > ve

Re: branch master updated: gnu: python-lxml: Update to 4.6.5.

Hi, On mar., 16 août 2022 at 09:51, Marius Bakke wrote: >>> > * gnu/packages/xml.scm (python-lxml): Update to 4.6.5. >> Now I see that python-lxml-4.7 shadows it. >> >> Note: This would have fixed two CVEs, CVE-2021-43818 and CVE-2021-43818. > > Can you add a "graft" for this version inst

Re: guix lint should support overrides

Hi Vagrant, On Tue, 23 Aug 2022 at 15:22, Vagrant Cascadian wrote: > But, because there is no way to silence a particular inappropriate > suggestion from guix lint, it becomes noise, and each person evaluating > the results of the package in the future then needs to take time to > figure out if

Re: FSDG issues of SCUMMVM-based games

Hi Liliana, (I have no opinion about this topic.) Your quote is: >> The data included in the source package represents the preferred form >> for modifications. >> If they were licensed under the G P L it would fail the "preferred >> form of modification" requirement but from the mentioned link

Re: Disarchive database includes tar.xz archives

Hi, Cool! On dim., 07 août 2022 at 19:27, Ludovic Courtès wrote: > Computing these has been possible since Disarchive 0.4.0, which Timothy > released in Dec. 2021 but we had not updated > ‘etc/disarchive-manifest.scm’ to disassemble tar.xz archives in addition > to tar.gz. I do not the rememb

Re: A real-life test of long-term reproducibility

Hi Ludo, On Fri, 02 Sep 2022 at 15:17, Ludovic Courtès wrote: > Here you would need ‘--allow-downgrades’. Maybe time-machine could advertise of this option? Well aside, it can be indeed confusing that the version-1.x branch does not match the tag v1.x; I understand why. --8<---cu

Re: Supporting upstream supported Python versions

Hi Ricardo, I am late to the party. :-) On Wed, 01 Jun 2022 at 09:50, Ricardo Wurmus wrote: > Here’s the manifest I came up with: By curiosity, why does package-with-explicit-python from (guix build-system python) not fit the bill? Cheers, simon

Re: Guix-devel Digest, Vol 109, Issue 56

Hi, I am late to the party. :-) On Fri, 22 Jul 2022 at 17:12, kiasoc5 wrote: > We could have packages recommend other packages to make this discovery > easier for users, like Arch's opt-depends. >From my point of view, ’recommend’ is like ’tag’. It is not well-defined and then it opens to man

Re: A real-life test of long-term reproducibility

Hi Konrad, On lun., 05 sept. 2022 at 09:49, Konrad Hinsen wrote: > Hi Ludo and Simon, > >> On Fri, 02 Sep 2022 at 15:17, Ludovic Courtès wrote: >> >>> Here you would need ‘--allow-downgrades’. >> >> Maybe time-machine could advertise of this option? > > And explain what it's about. I don't cons

Re: Idea: fallback for guix pull?

Hi, Sorry for the late reply. On sam., 06 août 2022 at 14:12, Christopher Rodriguez wrote: > I haven't looked at the code at all, but perhaps it would be useful to > users of Guix if, upon a guix pull with a commit that fails to > authenticate, guix pull would still pull up to the last in the c

Re: Failure with “guix copy“

Hi Ludo, On ven., 02 sept. 2022 at 15:35, Ludovic Courtès wrote: >> Well, I was expecting that the items were just copied. Why ‘guix copy’ >> tries to locally build something? > > My guess: use ‘--no-grafts’ and it’ll copy the ungrafted package. No, nothing is “grafted”. :-) Well, it is from a

Re: guix lint should support overrides

Hi Vgrant, On mer., 24 août 2022 at 14:06, Vagrant Cascadian wrote: > Maybe something like: > > (define-public thispackages > (package >(name "thispackages" >... >(lint-overides > (list > ;; The upstream name is actually "This Packages", not a typo. > "typo in d

Re: branch master updated: gnu: gitolite: Wrap programs instead of using propagated inputs.

Hi, On lun., 05 sept. 2022 at 13:08, "Thompson, David" wrote: >> https://ci.guix.gnu.org/build/1333185/details > ice-9/boot-9.scm:1685:16: In procedure raise-exception: > ERROR: > 1. &http-get-error: > uri: #< scheme: http userinfo: #f host: "141.80.167.131" > port: #f path: "/nar/zstd

How to write Guix extension?

Hi, Extension is a mechanism which allows to have more CLI subcommands. For example, see guix-modules or gwl; they extend Guix by providing the subcommands “guix module” or “guix workflow”. Note that: - guix-modules uses guile-build-system and is one file. - gwl uses gnu-build-system and is m

Re: How to write Guix extension?

Hi Ricardo, Thanks for explaining. On Wed, 07 Sep 2022 at 14:25, Ricardo Wurmus wrote: >> load-path: >> "/tmp/example/my" > > This is not correct. It should be /tmp/example. Indeed. > What doesn’t work is > > (use-modules (my top)) > (from-top) >

Re: [IDEA] lint the whole dang thang

Hi, On Wed, 07 Sep 2022 at 17:18, jgart wrote: > wdyt if we have the following option for `guix lint`? > > ``` > -f, --whole-file lint all the packages in the given file(s) > ``` I would prefer -m/--manifest first. :-) Cheers, simon

Sanitizer of record fields?

Hi, The website is currently failing [1] to build because a typo in some package declaration. The error message is not very helpful, srfi/srfi-1.scm:241:2: In procedure map: In procedure map: Wrong type argument: "https://www.qt.io/"; building pages in '/tmp/gnu.org/softw

Re: Sanitizer of record fields?

Hi, On Thu, 08 Sep 2022 at 11:32, Maxime Devos wrote: > On 08-09-2022 09:59, zimoun wrote: >> We could add a lint checker. Is it a “good” idea? > > We already have one, 'check-license'. Yeah, but I was talking about check if the field return the expected record type.

Re: Sanitizer of record fields?

Hi, On Thu, 8 Sept 2022 at 13:36, wrote: > > srfi/srfi-1.scm:241:2: In procedure map: > > In procedure map: Wrong type argument: "https://www.qt.io/"; > > building pages in '/tmp/gnu.org/software/guix'... > > > > ISTM this "wrong type argument" is an infuriatingly common

Re: nix installed with guix on a foreign distro

Hi, On Tue, 26 Jul 2022 at 01:00, jgart wrote: > How can we make it easier to install nix with guix on a foreign distro? Well, I think you need to manage some stuff by yourself. For example, write the nix-daemon service for starting/stopping; it depends on your distribution and it is probably

Re: guix import doesn't like newlines anymore :(

Hi, On Thu, 15 Sep 2022 at 19:10, jgart wrote: > Hi does anyone know why guix import does not insert newlines anymore? For which importer? Cheers, simon

Re: Store Functor and Store Applicative

Hi, On Sun, 18 Sep 2022 at 09:51, jgart wrote: > Why does Guix implement a monad but not a functor and an applicative? >From my understanding, because an appropriate and straightforward abstraction for the store is the State Monad. Maybe the implementator of the monadic stuff in Guix read righ

  1   2   3   4   5   6   7   8   9   10   >