Re: New “ungrafting” branch

Hello, On Tue, Dec 08, 2020 at 03:13:40PM +0100, zimoun wrote: > I have missed the discussion on IRC and I do not understand the > rationale. What's the point of "ungrafting"? I suppose it is just a branch with all the patches that are grafted applied, so that it is not necessary to graft them

Re: [support-re...@gandi.net: [GANDI] guixsd.org expires in 60 days]

Hello, On Sat, Dec 05, 2020 at 05:25:58PM +0100, Tobias Geerinckx-Rice wrote: > If cost is a pain point, note that Gandi's current annual renewal price of > €19 isn't the lowest around. cost is not the problem; but I like tidying up and getting rid of cruft, and I feel that this old domain is

[support-re...@gandi.net: [GANDI] guixsd.org expires in 60 days]

Hello all, just for your information, our domain name guixsd.org will expire soon (how many out there still remember that we own it?). We decided last year to renew it for just one more year and to let it run out. So if we still have anything pointing there, it would be good to change it now.

Re: Thank you for participating in the Guix Day!

Hello, On Tue, Nov 24, 2020 at 09:13:38PM +0530, Arun Isaac wrote: > Guix Day was wonderful. Thank you very much for organizing it! More than > anything, I attended just to see people's faces, and put faces to > names. Seeing smiling faces is surprisingly motivating, especially in > lockdown

Re: Using #true and #false everywhere?

On Wed, Oct 21, 2020 at 11:59:40AM +0200, Ludovic Courtès wrote: > What material are you referring to? SICP & co.? I simply used my favourite search engine with something such as scheme language boolean In my case the first link is to the racket manual:

Re: Using #true and #false everywhere?

Hello, On Tue, Oct 20, 2020 at 02:45:54PM +0200, zimoun wrote: > You are playing the devil's lawyer role, right? > This is a question about the standard, right? It is not about #true > or #false vs #t or #f. > The Guile manual explains well, isn't it? yes, indeed. What I want to say: Besides

Re: Using #true and #false everywhere?

And since we are on the bikeshedding front, I feel like writing a second message. On Fri, Oct 16, 2020 at 12:38:23PM +0200, Ludovic Courtès wrote: > As discussed on IRC recently, several of us think that using “#true” and > “#false” instead of “#t” and “#f” throughout or documentation and code >

Re: Using #true and #false everywhere?

Hello, on the bikeshedding front: I find #true and #false confusing, since everything I see on the Scheme language seems to use #t and #f. My first impression was that #true and #false were guilisms... On Fri, Oct 16, 2020 at 03:36:06PM +0200, Tobias Geerinckx-Rice wrote: > Maxim Cournoyer 写道： >

Re: Did nmap just become non-free?

Hello, On Thu, Oct 15, 2020 at 12:12:45AM +0200, Marius Bakke wrote: > Proprietary software companies wishing to use or incorporate Covered > Software within their programs must contact Licensor to purchase a > separate license. Open source developers who wish to incorporate parts > of

Re: 32-bit builds on 64-bit hardware/VMs

Hello, On Mon, Oct 12, 2020 at 01:52:18PM +0200, Ludovic Courtès wrote: > As a start, could you comment out in ‘machines-for-berlin.scm’ the > machines that need to be removed in order to not run 32-bit builds in > potentially buggy environments? already done by Danny in commit

Guix Europe yearly assembly minutes

Hello, the minutes of the yearly assembly of Guix Europe, which we held last June, are finally online: https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/guix-europe/minutes/ga-20200621.txt Enjoy, Andreas

Re: Release v1.2 timetable

On Tue, Oct 06, 2020 at 09:57:20AM +0200, Mathieu Othacehe wrote: > The CI is already building substitutes for two images > (hurd-barebones-qcow2-image and pine64-barebones-raw-image). We could > maybe release 1.2 version of those images. Nice! For completely selfish reasons, I would like to also

Re: 03/03: hydra: Update the file with the machines in the bayfront build farm.

Hello! On Sun, Sep 20, 2020 at 03:22:25PM +0200, Ludovic Courtès wrote: > ‘speed’ should be used with care: in general, you always want it to be > the same (not to be confused with ‘parallel-builds’). In the case > above, the risk is that milano will always be chosen. See

Re: Guix Paths

Hello, On Mon, Sep 21, 2020 at 01:32:52AM +, Buttery Pancake wrote: > I am wondering why Guix chose `/var/guix` path instead of `/gnu/var/guix` or > `/ > guix/var/guix`, as Nix uses `/nix/var/nix`? > I do think that having only one or two directories under root, `/gnu` and/or > `/ > guix`

Re: Packaging pd

Thanks for your replies, Ludovic and Ricardo! On Mon, Sep 07, 2020 at 12:22:45PM +0200, Ricardo Wurmus wrote: > > Now there already is a "pd" in Guix; are there any precedents on how to > > name a second pd? "pd-polytope"? "primal-dual"? "pd-primal-dual"? > “pd” in Guix is “Pure Data”, the visual

Re: IceCat-78.2 preview on 'wip-icecat-78' branch; need icedove-78.

Hello, On Mon, Sep 14, 2020 at 11:14:03PM +0200, Jonathan Brielmaier wrote: > ice-9/boot-9.scm:1669:16: In procedure raise-exception: > In procedure delete-file: No such file or directory just a quick guess: The nss recipe calls "delete-file" a few times in the replaced "install" phase. Maybe

Re: What should "guix build --source" produce? (was Re: Dependency cycle issues when using a Gexp-based snippet)

Hello Maxim, On Fri, Sep 11, 2020 at 02:22:44PM -0400, Maxim Cournoyer wrote: > +@cindex snippets, when to use > +The boundary between using an origin snippet versus a build phase to > +modify the sources of a package can be elusive. Origin snippets are > +typically used to remove unnecessary

Re: What should "guix build --source" produce? (was Re: Dependency cycle issues when using a Gexp-based snippet)

Hello Mark, On Tue, Sep 08, 2020 at 12:07:01AM -0400, Mark H Weaver wrote: > > + (let ((coreutils #+(canonical-package coreutils))) > > + (substitute* "configure" > > + (("/bin/pwd") > > + (string-append

Re: python-docker-py

On Fri, Aug 28, 2020 at 05:41:12PM +0200, Andreas Enge wrote: > Are you okay with renaming the package? There are only 2 dependent packages > (fdroidserver, on which I am currently working; and docker-compose)? Done in commit b8cb3eb63bf298d7b8965b3b41d45dce34771952. Andreas

Packaging pd

Hello, I knew that three letter software names are bad, but there is worse - two letter software names! I would like to package pd - Primal-Dual Methods for Vertex and Facet Enumeration http://www.cs.unb.ca/~bremner/software/pd/ Now there already is a "pd" in Guix; are there any precedents

python-docker-py

Hello, commit 3146b6da6dd3124f8693f48a9ed7ff8208324e23 moves python-docker-py from version 1.10.6 to 3.7.3. I think that at the same time, it should have been renamed to python-docker: - as can be seen in the source, it is downloaded from the "docker" project on pypi; - it advertises itself as

Re: Bootstrapping core-updates fails with mpc-1.2.1dev

I might have found the reason thanks to "guix build -K". Here are a few files in the gcc source directory: lrwxrwxrwx 1 andreas users 9 Aug 20 22:29 gmp -> gmp-6.0.0 drwxr-xr-x 15 andreas users4096 Aug 20 22:29 gmp-6.0.0/ lrwxrwxrwx 1 andreas users 9 Aug 20 22:29 mpc -> mpc-1.2.1

Bootstrapping core-updates fails with mpc-1.2.1dev

Hello, after the release of mpc-1.2.0, I tried to update the version in core-updates. More precisely, I used a tarball of the current master under the name of mpc-1.2.1dev, with an additional commit. Then bootstrapping fails. For someone with bayfront access, the build log is in

Re: MPFR and MPC

Hello, On Mon, Jul 27, 2020 at 12:58:52PM +0200, Ludovic Courtès wrote: > It’s gonna take a while, but I think we’d rather be safe than sorry > given that these two libraries underpin the toolchain chain (sic). oh well, never ask a question when you fear the answer might not be what you hope for

MPFR and MPC

Hello, mpfr just had a new release 4.1.0: https://ftp.gnu.org/pub/gnu/mpfr/ and I am planning to make one for mpc as well. Should I follow some procedure for an update in Guix, or could I just push two commits to core-updates? Andreas

Re: TeX Live 2019 wanted

On Mon, Dec 16, 2019 at 11:41:57PM +0100, Marius Bakke wrote: > Errh, the patch only works if you already have Poppler 0.83.0. For the > current 'core-updates' branch, I believe you can use the same approach > but fetch poppler-0.76.0.cc instead (or take Arch's patch[0]). Ah, this is rocket

Re: Profiles/manifests-related command line interface enhancements

Hello, I am reading up on old threads during the holiday season... On Sun, Nov 17, 2019 at 12:30:11PM +0100, Konrad Hinsen wrote: > If enough people are willing to work on this (beginners included!), we > could run a "CLI working group" that plays with alternatives to the > current CLI,

Re: TeX Live 2019 wanted

I gave it a try, dropped the patches, then the phase use-code-for-new-poppler fails for texlive-bin; maybe these poppler phases can be dropped, but I am not quite familiar with them. Andreas

Re: TeX Live 2019 wanted

Hello, On Sat, Dec 14, 2019 at 08:06:19PM +0100, Marius Bakke wrote: > Ricardo, do you think you'll have time for a TeX Live 2019 update in the > coming weeks? If not, could you outline the required changes for > enterprising Guix contributors? before your mail I had already tried to update the

Re: The Guix Days: stream?

On Thu, Dec 12, 2019 at 06:57:27PM +0100, zimoun wrote: > Previously, we discussed on the possibility to video stream chunks of > these 2 days. Honestly, I do not think it is a good idea for an "un-conference". These two days are more devoted to hacking, hands-on activities and spontaneous

Re: Python package naming: Dots vs hyphens

Hello, On Wed, Nov 06, 2019 at 07:49:56AM +0100, pelzflorian (Florian Pelz) wrote: > Shall I rename python-zope-* to python-zope.*? the package naming guidelines say "replace underscores by hyphens". I would extend this to say "replace punctuation marks by (one) hyphen". Probably when we wrote

Re: qt4 packages

On Mon, Jul 15, 2019 at 09:17:02PM +0300, Efraim Flashner wrote: > texmacs Debian dropped 2(?) versions ago I just added it during the Guile/Guix days at Strasbourg, please do not drop it... Also, it is a GNU project. It may have been removed from Debian because it depends on guile-1.8; but there

Re: Cuirass Ghzminutes enhancement idea

On Fri, Jun 21, 2019 at 05:43:54PM +0200, swedebugia wrote: > Maybe we could have an additional time measurement: Ghzminutes. > E.g. if the build took 60 minutes on a 3 Ghz machine it took 20 Ghzminutes. 180 GHzmin? Andreas

Re: 01/01: gnu: Add libgd.

On Thu, Jun 20, 2019 at 12:43:41PM +0200, Nicolas Goaziou wrote: > But, isn't the project's name libgd? I would say so. It is the domain name and also the tarball name. The website starts with a news item: "The LibGD team is proud to announce the 2.2.5 release of libgd." But renaming it now

Re: 01/01: gnu: Add libgd.

On Thu, Jun 20, 2019 at 11:06:47AM +0200, Ludovic Courtès wrote: > This library is already available as ‘gd’ in (gnu packages gd). :-) Ah, I overlooked it also! Probably because I looked for "libgd" or "gdlib". Andreas

Re: 01/01: gnu: Add ratpoints.

On Thu, Jun 20, 2019 at 11:04:35AM +0200, Ludovic Courtès wrote: > > +++ b/gnu/packages/patches/ratpoints-sturm_and_rp_private.patch > Could you add a sentence or two explaining what the patch does and what > its upstream status is? This is especially important for non-trivial > patches like this

Re: Difference between Scintilla's license and ISC

Hello! I do not get why the license can be free with the non-commercial clause. What am I misunderstanding? Andreas

Re: Difference between Scintilla's license and ISC

Hello, I think that the Scintilla license is non-free... On Wed, Jun 19, 2019 at 01:24:15PM +0200, Nicolas Goaziou wrote: > Permission to use, copy, modify, and distribute this software and > its documentation for any purpose and without fee is hereby granted, > > and the ISC license

Re: Packaging Sagemath

On Tue, Jun 18, 2019 at 01:30:06PM +0200, Andreas Enge wrote: > We may as well delete the packaged > items (as I have been doing for two or three I just packaged now), and > leave only TODO items. Well, no; I have actually kept packages that I did not yet add to my preliminary sa

Re: Packaging Sagemath

On Tue, Jun 18, 2019 at 11:47:29AM +0200, Nicolas Goaziou wrote: > I followed the link, but, IIUC, it is not up-to-date. For example, we > already have packaged many of them. Would it be useful to set-up > a world-writable document (e.g., a pad) somewhere, with a list of the > packages yet to be

Packaging Sagemath

motivated to package one or the other we do not have yet, you are more than welcome! Andreas ;;; GNU Guix --- Functional package management for GNU ;;; Copyright © 2019 Andreas Enge ;;; ;;; This file is part of GNU Guix. ;;; ;;; GNU Guix is free software; you can redistribute it and/or modify

Re: Digimend kernel drivers for Guix

Hello Tobias, you do not like false things, do you? On Tue, May 28, 2019 at 08:33:29PM +0200, Tobias Geerinckx-Rice wrote: > Tobias Geerinckx-Rice wrote: > > However, in this case, please use the even simpler: > > (arguments > > '(#:tests?)); no test suite > >

Re: guile-bash updated source url

Hello, On Sun, Apr 28, 2019 at 10:28:43AM +0200, david.lars...@selfhosted.xyz wrote: > This is my first contribution to guix and it's just a minor fix for > the guile-bash package which had an outdated source url. I was able to > retrieve the same revision of the package via the software-heritage

Re: Error building linux-libre on Overdrive 1000

On Tue, Apr 09, 2019 at 04:37:09PM +0200, Tobias Geerinckx-Rice wrote: > ‘guix system init’ fails for me in the following way on the following > version: > > $ guix describe > Generation 4Apr 08 2019 23:29:08(current) > guix 2afb793 > repository URL:

Re: 05/15: gnu: wesnoth: Rename package to the-battle-for-wesnoth.

On Fri, Mar 29, 2019 at 03:02:00PM +0100, Tobias Geerinckx-Rice wrote: > I still think this change should be reverted I also think so. The wording in the naming guidelines is intentionally a bit vague; the intention was definitely to take in general the tarball name, or maybe if this does not

Re: 06/15: gnu: wesnoth-server: Rename package to the-battle-for-wesnoth-server.

Hello, On Tue, Mar 26, 2019 at 04:32:46PM +0100, Pierre Neidhardt wrote: > Sorry, I misunderstood the conclusion of the discussion: I thought that > we would simply follow the package naming convention as per the manual. I am confused about this statement. The naming convention speaks a bit

Re: bug#25970: mozjs build failure

Hello, On Mon, Feb 04, 2019 at 11:27:05PM +0100, Leo Famulari wrote: > The package in question, mozjs 24, is no longer used by gnome-shell, or > by any other Guix package. > > So, if it still fails to build, we can consider removing it. the package builds, but I see no need to keep it. Do you

Re: Eliminate environment variable hints?

Hello, On Tue, Feb 19, 2019 at 08:41:47AM +0100, Ricardo Wurmus wrote: > This only needs to be done when GUIX_PROFILE is not set. The > definitions in etc/profile either reference /gnu/store directories > directly (when GUIX_PROFILE is not set) or they reference the profile > links (when

Re: Eliminate environment variable hints?

Hello, On Mon, Feb 18, 2019 at 10:56:13PM +0100, Ricardo Wurmus wrote: > when installing a package into a profile Guix very helpfully tells you > that you may need to set certain environment variables. It doesn’t tell > you that these environment variables can also be set by source’ing the >

Re: Policy to remove obsolete packages

On Mon, Feb 04, 2019 at 12:16:12PM +0100, Björn Höfling wrote: > If a package is broken for more than 6 months, we should just remove it > from Guix. Prior to removing, we should announce on the dev mailing > list, maybe someone will care about it then. If there is no response > within 2 weeks, we

Re: Meeting in Brussels on Wednesday evening?

On Tue, Jan 29, 2019 at 10:52:18AM +0100, Ludovic Courtès wrote: > I’d be available tomorrow (Wed. 30th) at around 8PM in Brussels. > Would anyone be willing to join for a drink + dinner? > We could meet at “Au Bon vieux temps”¹ (it’s a must!) and then head to a > neighboring restaurant. Sorry

Re: Guix Days starting in two days!

On Tue, Jan 29, 2019 at 10:58:24AM +0100, Ludovic Courtès wrote: > We’ll update as > needed to share practical info. Please email Pjotr, Manolis, Ricardo, > or myself if you have any questions. And since we need to book food now, please tell

Re: Changes in the spending committee for the FSF Fund

Hello, On Fri, Jan 25, 2019 at 11:57:21PM +0100, Ludovic Courtès wrote: > There’s a ledger for the Guix Europe non-profit¹, which is a separate > entity, but most of the transactions on the funds held at the FSF have > been made via Guix Europe. And the decisions of the Solidary Administrative

Re: bug#33676: GuixSD on eoma68-a20?

On Sat, Dec 15, 2018 at 02:04:58PM -0500, Mark H Weaver wrote: > >> See also > >> https://blog.merovius.de/2013/10/20/ext4-mysterious-no-space-left-on.html > > It was, and I disabled it. Hopefully this does not break anything... > Why did you disable it? Because we get exactly these spurious

Re: bug#33676: GuixSD on eoma68-a20?

On Fri, Dec 14, 2018 at 09:50:26PM +0100, Danny Milosavljevic wrote: > can you check whether dirindex (hashtables for directory) is enabled? > # tune2fs -l /dev/... | grep -o dir_index > See also > https://blog.merovius.de/2013/10/20/ext4-mysterious-no-space-left-on.html It was, and I disabled

Re: GuixSD on AArch64

Hello Vagrant, On Mon, Oct 22, 2018 at 12:17:58PM -0700, Vagrant Cascadian wrote: > Looking like u-boot 2019.01 might be more likely, but modest patches > work with 2018.11-rc2. I'll probably bring the pinebook with me to the > Paris meetup in December... though with only 2GB of ram it might not

Re: End of beta soon? drop i686?

On Wed, Dec 12, 2018 at 03:16:56AM +0100, Ricardo Wurmus wrote: > > I'm opposed to dropping i686 support. If we dropped support for systems > > that are not well supported in Guix, the only system left standing would > > be x86_64-linux. I believe it is of paramount importance that Guix be > >

Re: bug#33676: GuixSD on eoma68-a20?

Hello Danny, On Mon, Dec 10, 2018 at 11:30:14AM +0100, Danny Milosavljevic wrote: > I've tried it now and I get: > dannym@bayfront ~/src/guix$ ./pre-inst-env guix system disk-image > --system=armhf-linux gnu/system/install.scm > ... > importing file or directory >

Re: bug#33676: GuixSD on eoma68-a20?

Hello Danny, On Sat, Dec 08, 2018 at 06:12:14PM +0100, Danny Milosavljevic wrote: > Guix received one but we have so far be unable to get the GuixSD flash > image because something always breaks on Hydra before it's done although the problem seems to lie somewhere else, I would just like to

Re: [bug#33600] [PATCH 0/3] Defaulting to ci.guix.info (aka. berlin.guixsd.org)

On Tue, Dec 04, 2018 at 11:28:51AM +0100, Ludovic Courtès wrote: > Awesome. I’ve added a file to record that info in > guix-maintenance.git. Please feel free to complete it; for instance > it’d be good to know the expiration date of each domain. Done for guixsd.org. It expires on January 27. I

Re: [bug#33600] [PATCH 0/3] Defaulting to ci.guix.info (aka. berlin.guixsd.org)

On Tue, Dec 04, 2018 at 10:03:01AM +0100, Ludovic Courtès wrote: > As for guixsd.org, it was initially owned by Andreas Enge who > transferred it to Guix Europe and also provided credentials to me and I > think a couple of other people, though I forgot who. Andreas? Apart from you, t

Re: [bug#33600] [PATCH 0/3] Defaulting to ci.guix.info (aka. berlin.guixsd.org)

On Mon, Dec 03, 2018 at 06:44:43PM -0500, Mark H Weaver wrote: > Who owns the guix.info domain? Also, who owns the guixsd.org domain? guixsd.org is owned by the Guix Europe association. guix.info, as far as I know, by Ricardo. Plans are to drop guixsd.org in the long run, and I would suggest to

Re: mips64el machine - mrustc

Hello Danny, I have a mips64 machine (the mini-pc desktop version of Mark's laptop, with only one core). It is excruciatingly slow (if I remember well, just compiling guix takes a few hours) and makes a tractor like noise, so I turned it off and moved it to my closet. But I could take it out

Re: FSDG status of chromium

Hello, On Tue, Sep 25, 2018 at 09:08:42PM +0200, Marius Bakke wrote: > That leaves "first party" source files. Admittedly I haven't audited > all of those other than superficial grepping. Do you know whether parts > of Chromium are considered non-free? I noticed a number of files are > missing

Re: What ARM hardware should we buy and where should we host it?

On Fri, Sep 14, 2018 at 11:37:25PM +0200, Ricardo Wurmus wrote: > Thanks for sharing this. In my opinion, it would be good if we could > increase the number of build machines first before we allow too much of > the funds to be regularly consumed by hosting costs. Indeed, I just mentioned it to

Re: Blog: Guix packaging tutorial

Hello Pierre, nice idea! I agree with Ricardo's suggestions. You could have a look at the slides of a talk I gave at GHM 2013 in the "maintenance" git repo, inside the talks/ghm-2013/andreas directory. Some things are outdated (we did not have the macros to manipulate build phases yet). There I

Re: What ARM hardware should we buy and where should we host it?

Hello, On Mon, Sep 03, 2018 at 01:37:54PM +0200, Ricardo Wurmus wrote: > The first question is what ARM hardware to buy; the second is where to > host that hardware. Here are some considerations: concerning hosting, I could easily host one smaller machine (like the Overdrive 1000) in my living

Re: FOSDEM 2019 - stand

I will probably attend FOSDEM again, and if I do, then I would like to spend a slot at the stall. On Sun, Sep 09, 2018 at 03:13:57PM +0200, Tonton wrote: > I have some stickers [1]; I might > get more of the same, but slightly bigger. I'll bring what I have - if I can. We should be able to

Re: Guix on aarch64

Hello, On Tue, Aug 28, 2018 at 09:57:49AM +0200, Ricardo Wurmus wrote: > I can remove one of the build machines from Berlin. would this not aggravate the problem with the availability of substitutes? As I understand it, then we would have two separate machines, each of which would build the same

Re: RFC: Portability should be a higher priority for Guix (was Re: 01/01: build-system/meson: Really skip the 'fix-runpath' phase on armhf.)

Hello, On Thu, Jul 05, 2018 at 11:04:31AM +0200, Jonathan Brielmaier wrote: > I just want to bring POWER up as a freedom-respecting architecture. > Especially the TalosII from RaptorCS[0]. I know that guix does not work > on ppc64le yet, but I'm working for it :) They tend to be quite >

Re: RFC: Portability should be a higher priority for Guix (was Re: 01/01: build-system/meson: Really skip the 'fix-runpath' phase on armhf.)

Hello all, of course I can all but agree that support for "exotic" hardware is very desirable, especially since, as Mark pointed out, we would like it to become more mainstream! On Thu, Jul 05, 2018 at 08:38:19AM +0200, Ricardo Wurmus wrote: > One thing that would help, in my opinion, is to

Re: a92d97266 seems to break master

Hello, On Tue, May 22, 2018 at 12:56:55AM +0800, Alex Vong wrote: > a92d97266dffcd1ab5c40a379005a7db1fc3dad4 seems to breaks master with the > following error: > make[2]: *** No rule to make target 'gnu/packages/patches/pius.patch', needed > by 'all-am'. Stop. apologies, my mistake! I forgot

Re: Shepherd release!

On Mon, Mar 19, 2018 at 05:42:11PM +0100, Ludovic Courtès wrote: > You probably need to run ‘gettextize’ first. That is strange, why have I never heard about this command before? Anyway, I tried, and it shows a lot of scary warnings: ... Updating Makefile.am (backup is in Makefile.am~) Updating

Re: Shepherd release!

Hello! On Fri, Mar 16, 2018 at 01:44:37PM +0100, Ludovic Courtès wrote: > For the record, it can be tested on GuixSD by running “make dist” in the > Shepherd and then applying a patch like this in Guix: I am already failing in getting the shepherd configured. On a fresh git checkout, I do

Re: Language tag for traditional Chinese

Hello, On Tue, Mar 06, 2018 at 08:35:46PM +0800, Alex Vong wrote: > I also want to add tranditional Chinese translation to guix in the > future (after I figure out how to use handwriting recognition). I think > I will still use the zh_TW since I think it is an established convention > for distro.

Re: 0.14.1?

On Mon, Mar 05, 2018 at 06:07:07PM +0100, Ricardo Wurmus wrote: > Now that so much time has passed and so many packages have been added > and updated we could even do 0.15.0. This should be one of the few pleasures of the release managers, to decide about version numbers and code names! Andreas

Re: 0.14.1?

On Mon, Mar 05, 2018 at 10:41:34AM +0100, Ludovic Courtès wrote: > I would like to add the new Shepherd as well, which should be ready > anytime soon. It would be important to fix bug https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30299 first, and maybe other shepherd related bugs in the

Re: Nginx service fails

Hello, On Mon, Mar 05, 2018 at 12:43:35AM +0100, Andreas Enge wrote: > $ guix system reconfigure AE/clementi.scm > guix system: error: failed to load 'AE/clementi.scm': > AE/clementi.scm:5:0: In procedure allocate-struct: Wrong type argument in > position 2: 25 I think I know the an

Re: bug#30706: Nginx service fails

On Mon, Mar 05, 2018 at 08:23:18AM +0100, Ricardo Wurmus wrote: > I had the same error when updating my i686 netbook after a long while. > After a reboot everything seemed to be fine, though. Ah, thanks for the information! A reboot made things worse in my case - I rebooted the virtual machine,

Re: Nginx service fails

PS: I rebooted the virtual machine, and now it looks as if even the openssh service did not start: ... port 22: Connection refused :-(

Re: Nginx service fails

Hello Danny, thanks for your quick reply! On Mon, Mar 05, 2018 at 12:07:44AM +0100, Danny Milosavljevic wrote: > find-long-options is supposed to be in gnu/build/linux-boot.scm and > gnu/services/base.scm is using it. > > It's in there for some weeks now... > > You can find out where guix is

Re: Nginx service fails

Well, I am turning this into a bug report, since it still occurs with the latest git commit ac1a9ce8b07f3b80900ee08436ff6e683e8dc195 . This is the result of "./pre-inst-env guix system reconfigure ...", where "..." is my configuration file: ... creating nginx log directory '/var/log/nginx'

Nginx service fails

Hello, writing to guix-devel first, since I am not sure whether I should file a bug report. When reconfiguring my virtual machine today after I had added a virtual host to nginx, it failed with the following error message: ... creating nginx log directory '/var/log/nginx' creating nginx run

Re: Posts in languages other than English on help-guix?

On Fri, Mar 02, 2018 at 08:31:36PM +, ng0 wrote: > To not pick the generischer Maskulinum (which would be contrary the rest of > our > Documentation guidelines) Indeed, it is difficult to write grammatically and syntactically correct, pleasant to read, gender neutral German! I am not a fan

Re: Posts in languages other than English on help-guix?

On Fri, Mar 02, 2018 at 04:47:45PM +, ng0 wrote: > On topic: I think it's too much to suggest to include something that indicates > the language of the post in the subject? I think people will easily recognise languages they speak in a post! Andreas

Re: Posts in languages other than English on help-guix?

Hello! On Fri, Mar 02, 2018 at 05:02:40PM +0100, Ludovic Courtès wrote: > What about allowing posts on help-guix in one of the languages that > regular contributors know, in addition to English? That sounds like a good idea. However, in the text, I would still say that English is the preferred

Re: Kernel modules in initrd

Hello, On Fri, Feb 23, 2018 at 03:28:55PM +0100, Danny Milosavljevic wrote: > No, wait, according to > https://unix.stackexchange.com/questions/43699/debian-does-not-detect-serial-pci-card-after-reboot/43723#43723 > , > the kernel should be doing that even without udev. Are we sure we need to

Re: Kernel modules in initrd

Hello Danny, On Thu, Feb 22, 2018 at 10:34:03PM +0100, Danny Milosavljevic wrote: > When you booted from the USB key the system DIDN'T need mptsas to find > ITS root filesystem. So it booted fine and in the end of it all you had > a working GNU Linux, with udev. > > Then udev saw the hard disk

Kernel modules in initrd

Hello, recently I had an unpleasant experience in installing GuixSD: After booting with the USB key and following the installation instructions, then rebooting into the installed system, the "/" file system was not found: neither using file system labels, nor device nodes. The problem turned out

Re: Staging

On Tue, Feb 20, 2018 at 03:14:39PM +0200, Efraim Flashner wrote: > CMake is just old, not especially in need of updates. It would be nice > to ungraft stuff though. I just meant to not switch cmake versions together with other things: $ ./pre-inst-env guix refresh -l cmake Building the following

Re: Staging

On Tue, Feb 20, 2018 at 06:57:06AM -0500, Leo Famulari wrote: > On Tue, Feb 20, 2018 at 11:45:58AM +0200, Efraim Flashner wrote: > > Java currently only affects x86_64, so I'm not sure that it would need > > to be staging specifically. In any case if we can get it merged within > > the next week

Re: heads-up: Haskell updates

Hello Ricardo, On Sat, Feb 17, 2018 at 02:04:31PM +0100, Ricardo Wurmus wrote: > I’ve built ghc-resourcet successfully with this change. I’d be happy if > those of you who reported build failures could please retry building > ghc-resourcet with current master or core-updates (the fix to ghc-mtl

Re: heads-up: Haskell updates

On Thu, Feb 15, 2018 at 12:04:04PM +0100, Danny Milosavljevic wrote: > So I suspect that Ricardo has a Linux >= 4.5 but Andreas and Hydra > have a Linux < 4.5. Is that correct? Strangely not. I am running Guix on Debian with a kernel 4.9.0-5-amd64. Andreas

Re: Call for project proposals: Guix and Outreachy

Hello Gábor, quite a list of interesting ideas! On Wed, Feb 07, 2018 at 08:51:10AM +0100, Gábor Boskovits wrote: > 10. provide user interface to our build farm where we could request building a > specific package. This is one specific feature, but could be framed into a more general project of

Re: Call for project proposals: Guix and Outreachy

Hello Ricardo, On Tue, Feb 06, 2018 at 11:05:34PM +0100, Ricardo Wurmus wrote: > * User interface improvements your project sounds very interesting, it has some technical components, but might also attract some more diverse talents with its focus on more general usability. I also like that you

FOSDEM Saturday dinner

Hello, not having our own room makes it difficult to coordinate! Let us meet somewhere after the talks to go together for dinner. As an easy to find meeting point, I suggest in front of the food place in Janson at 19h. See you soon, Andreas -- Sent from my Android device with K-9 Mail.

Re: Guix key signing party at FOSDEM?

Good point! I would suggest tomorrow, so we have a chance of printing our keys at the hotel. Andreas On 3 February 2018 15:14:24 CET, Chris Marusich wrote: >Hi everyone, > >It was a pleasure meeting many of you yesterday at the GNU Guix >meet-up! > >Some people expressed

Re: Porting GuixSD to ARM article.

Hello, On Tue, Jan 23, 2018 at 10:23:50AM +0100, Mathieu Othacehe wrote: > > Notice that the last section of the blog post does not solve the problem: > > As I realised by trial and error when trying to use a disk-image for a > > virtual machine, it really is only an installation-image,

Re: Porting GuixSD to ARM article.

Hello Mathieu, On Fri, Dec 22, 2017 at 02:12:02PM +0100, Mathieu Othacehe wrote: > A new article is available on Guix's website. It summarizes recent > progress on ARM porting topic. I am reading it only now (since I wish to install GuixSD on an ARM board of mine, but better late than never...).

Guixsd.org domain

Hello all, just for your information, I am in the process of moving the guixsd.org domain from my personal account to Guix Europe and also to a different registrar. I suppose that the DNS records will just move with it, but I am not totally sure; so if servers appear to be unreachable, this might

<    1   2   3   4   5   6   7   8   9   10   >