Re: Policy to remove obsolete packages
Hi simon, On Thu, 7 Feb 2019 13:40:53 +0100 zimoun wrote: > Hi, > > I understand but I am not sure to see the points and/or advantages > about a policy. > > From my opinion, obsolete package is not well-defined and define > cleanly what an obsolete package is will be bikeshedding. :-) > And I think that deprecated should come from upstream. > However, a popcon of the downloaded substitutes should provide which > packages are "important" and which are less; to have a better > "priority list"---if needed. I really wouldn't take that "Policy" too formal: It is more like that: There are packages that are just broken and nobody cares. But nobody removed them from Guix, because everybody was unsure about it. Now we agreed on that when a package is broken for more than 6 months we should announce it on dev-list and if then nobody takes action, we remove it. It is more like "community consensus" that it is very OK to remove these packages. CI is another related topic we are working on. In theory, a commit should break nothing. Or at least the commiter should get a message back of what exactly they broke. > And I also do agree that it is hard to find the information what it > went wrong. For example, recently I was not able to find what breaks > clang@3.5. Sometimes it magically helps to just write a bug-report with the correct error-message and/or link to hydra.gnu.org's failure. I noticed in the past that a good, concise bug-report gets attention to the right people to fix it :-) Björn pgpZh_sQY8MZH.pgp Description: OpenPGP digital signature
Re: Video documentation repository
On Thu, 07 Feb 2019 20:31:30 +0100 Ludovic Courtès wrote: > > In the current video-repository we at least save the input binaries > > (i.e speech recordings in several languages for several videos). > > From your comment it sounds like that is not intended for the > > savannah-repos, right? > > True. I mostly wanted to reassure them that this would not be a huge > repo containing only binary files. So I guess it’s OK to save audio > tracks as long as it doesn’t grow too much. > > If/when it happens to grow quickly than expected, we’ll ask the > Savannah folks whether it’s still fine with them. OK. So when the repository is created, we will save the input audios to it, but not the output videos. Thanks, Björn pgpdEEbOp_W8M.pgp Description: OpenPGP digital signature
Re: News from the Guix Days!
On Thu, 07 Feb 2019 20:37:53 +0100 Ludovic Courtès wrote: > I’d like to invite the other participants :-) to either prepare a > Markdown-formatted summary of their session to publish on the blog¹ > (make sure it’s understandable by outsiders too!), or to send their > notes or memories of the discussions on this list. Thanks Efraim, that blog post looks pretty cool! I added my writings here: https://libreplanet.org/wiki/Group:Guix/FOSDEM2019#Sessions_Outcome Though I have to admit they are not as nice as the blog-post. @Ludo: Especially with the Cuirass-Session I was a bit lost. Would you like to add a bit more and/or delegate to the right persons? Björn pgpvWN2MmoAxm.pgp Description: OpenPGP digital signature
Re: New videos: topic daily use.
On Wed, 06 Feb 2019 23:17:21 +0100 Ricardo Wurmus wrote: > Hi Laura, > > > My next video will be about daily using of Guix. > > Neat! +1 > > I was thinking of daily use of guix package, mentioning profile, > > generations (both the concepts and commands to deal with them) > > Sounds good. “--install”, “--roll-back”, and maybe even “--manifest” > for stateless installations would be good topics to cover. Is "--manifest" really "daily use" for a Guix newbie? I would disagree and first stick to the "--install" --"remove "--rollback" "--list-generations" mode. > > > but > > also about guix pull and guix gc. > > The videos should be about 3 min length (+/-) 1. > > Do you think that they should be included in the same video or split > > them in two? > > I think “guix pull” deserves its own video, because it can be combined > with channels. I would mention the simplest version of "guix pull", i.e. the way it is set up by default with the "default" channel. I think it is a really important tool, compared to "apt-get update" on Debian. We can then put the more complicated parts like channels into another video, but I think that a simple "guix pull" MUST be in here. > Same with “guix gc”, because it has a bunch of features other than > garbage collection. I have no strong opinion here. Björn pgpulldY4T2yN.pgp Description: OpenPGP digital signature
Re: Patchwork + automated checking and testing of patches
Ludovic Courtès writes: > Heya! > > Christopher Baines skribis: > >> So, today at the Guix Days event in Brussels I've made a small change to >> the Laminar configuration related to patchwork.cbaines.net. > > Damn it, I didn’t know you had done that while we were there, kudos! > >> Now, when processing a series of patches, it should create a Git branch >> and push it to a repository. >> >> For example, for this patch series [1], you can see it being processed >> here [2]. The result of applying the patches is pushed up to this Git >> repository [3], and you can see the commit range here [4]. >> >> 1: https://patchwork.cbaines.net/project/guix-patches/list/?series=482 >> 2: https://laminar.cbaines.net/jobs/patchwork-test-series/826 >> 3: https://git.cbaines.net/guix/patches/log/?h=series-482-version-1 >> 4: >> https://git.cbaines.net/guix/patches/log/?h=series-482-version-1&qt=range&q=base-for-series-482-version-1..series-482-version-1 > > Neat! Thanks, however, one thing I've noticed is that git apply seems to be much more reliable at applying patches than git am. It often fails with "Patch is empty". I'm not sure why, it seems to work for the patches I've sent with git send-email, but maybe it's very particular about the formatting... >> I'm hoping that having the patches in a Git repository can enable using >> things like `guix pull` to build a Guix with the patches to then extract >> information about what's changed, as well as potentially being useful >> for getting Cuirass to build things... > > Yup, this is really promising, looks like you’re getting there! As > discussed at the Greek restaurant, it’d be nice to see how much of the > job Laminar runs can be turned into (guix …) modules, though that can > come later. > > Anyway, as this is shaping up, let us know if you need input on the > remaining bits, like using the channel API to extract information about > the new branch, or fiddling with Cuirass. I've made a bit more progress with this over the last couple of days, I'll start another thread for that though. Thanks, Chris signature.asc Description: PGP signature
Tracking and inspecting how Guix changes over time
In summary, I've started playing around with a new service, I'm currently calling it the "Guix Data Service". The code is here [1], it's based off of Ricardo's excellent Mumi, and at the moment only does one thing, a basic comparison of two different versions (commits) of Guix for the few commits it has data for. I've got it up and running here [2]. 1: https://git.cbaines.net/guix/data-service/ 2: https://prototype-guix-data-service.cbaines.net/ This follows on from the work around reviewing patches for Guix, at the moment, I've setup Patchwork [3] to gather up patches sent to guix-patches, Laminar [4] to apply those patches to the Guix master branch and then push the resulting changes to a git repository [5]. 3: https://patchwork.cbaines.net/project/guix-patches/list/ 4: https://laminar.cbaines.net/ 5: https://git.cbaines.net/guix/patches/ To get to the point where as part of some automated review process, packages affected by patch series can be built, and then the results of this compared with the previous state in Guix, it's necessary to understand if the packages currently build successfully, and then you need to check if those same packages build with the patches applied. This is what I'm attempting to work towards with this new service. You give it a commit and a repository URL. It then fetches that revision of Guix using the same mechanism as guix pull, and extracts the information about packages through the Guix inferiors code. This information about packages is then stored in the database. For querying, you provide two commits, and the comparison is generated from the information stored in the database. It displays new packages, removed packages, packages where the available versions have changed, and then "Other changed packages" which are ones where the metadata (synopsis, description, home-page, ...) or derivation has changed. I've hooked this up to Patchwork and Laminar, so you can see some initial data in the following 3 examples. The following links relate to a couple of patches affecting the Ruby build system. Issue:https://issues.guix.info/issue/34385 Patchwork series: https://patchwork.cbaines.net/project/guix-patches/list/?series=535 Laminar job: https://laminar.cbaines.net/jobs/patchwork-test-series/889 Git commits: https://git.cbaines.net/guix/patches/log/?h=series-535-version-1&qt=range&q=base-for-series-535-version-1..series-535-version-1 Comparison: https://prototype-guix-data-service.cbaines.net/compare?base_commit=6fd72f7094885dc3dbb10431996c445251094915&target_commit=7d70e05d7064f31a8de60b04d22ac16c1953b7a9 The following links relate to some printing changes in Gnome. Issue:https://issues.guix.info/issue/34240 Patchwork series: https://patchwork.cbaines.net/project/guix-patches/list/?series=482 Laminar job: https://laminar.cbaines.net/jobs/patchwork-test-series/886 Git commits: https://git.cbaines.net/guix/patches/log/?h=series-482-version-1&qt=range&q=base-for-series-482-version-1..series-482-version-1 Comparison: https://prototype-guix-data-service.cbaines.net/compare?base_commit=bc041b3e264380bd49025515d3c5d11319aa3f50&target_commit=e396076117623efb6351b845ec61b4572457c3e0 The following links relate to some new Ruby packages. Issue:https://issues.guix.info/issue/34217 Patchwork series: https://patchwork.cbaines.net/project/guix-patches/list/?series=474 Laminar job: https://laminar.cbaines.net/jobs/patchwork-test-series/887 Git commits: https://git.cbaines.net/guix/patches/log/?h=series-474-version-1&qt=range&q=base-for-series-474-version-1..series-474-version-1 Comparison: https://prototype-guix-data-service.cbaines.net/compare?base_commit=bc041b3e264380bd49025515d3c5d11319aa3f50&target_commit=0645e6beb8c1a8818c3764a42dcc8598c8711e7b So, in terms of reviewing patches, I don't think this isn't actually that helpful, yet. I would guess that it's still more useful to look at the actual patches. However, I think this kind of information could be useful in the future, for example checking that patches that shouldn't affect any derivations indeed don't, or providing a more general way of assessing the number of rebuilds that a patch series would cause. I've also gone with this very general approach of a service to handle data relating to Guix, as I think it could be useful for purposes other than reviewing patches, assessing security issues for example. In terms of building the packages that correspond to patches, one way forward that I have in mind is to somehow get a Cuirass instance to build the branch corresponding to a patch series. Then, work out what packages have been affected by querying the "Guix Data Service". Then query Cuirass to work out if those affected packages built before the changes, and also if they build with the patches applied. Going back to this new service though, I've hooked it up to the patchwork-test-series [6] job in Laminar. It enqueues a jo
Inverting command line session colours
Hi Guix! I am having trouble inverting the colours of the command line session videos. They should be black in the foreground with white text. Gábor, I guess you solved that, could you remind me how you did it? There was a link with -negate in convert but did not work for me. Regards :) Laura
Issue with my version of guix
Hi Guix! i have an issue with my guix version. It seems to have not been upgraded to guix 0.16.0, even I have the new commands. This is the output of my guix --version, which shows a commit. guix --version guix (GNU Guix) 9d58e8819fdbc4c1c8a1ef6149e2d2376731a6a6 Copyright (C) 2019 the Guix authors And both for installing stuff with guix package or even guix pulling, I need to add the subsitute option for using https://ci.guix.info Otherwhise it uses the mirror from hydra. Do you know what I am missing here? Regards :) Laura
Re: Issue with my version of guix
Hi Laura, On Fri, 8 Feb 2019 12:25:41 -0300 Laura Lazzati wrote: > This is the output of my guix --version, which shows a commit. > guix --version > guix (GNU Guix) 9d58e8819fdbc4c1c8a1ef6149e2d2376731a6a6 > Copyright (C) 2019 the Guix authors This commit seems to be very recent, so not sure what you mean. (it's from Feb 8 2019) > And both for installing stuff with guix package or even guix pulling, > I need to add the subsitute option for using https://ci.guix.info > Otherwhise it uses the mirror from hydra. That's weird... Is your guix-daemon also recent? Try: /proc/$(pidof -s guix-daemon)/exe -V in order to find out its version. What does it say? Does your system configuration in /etc/config.scm specify custom substitute-urls ? pgpT0Swm1xBek.pgp Description: OpenPGP digital signature
Re: Issue with my version of guix
Hi Danny :) > This commit seems to be very recent, so not sure what you mean. > (it's from Feb 8 2019) Yes, I guix pulled today. > > > And both for installing stuff with guix package or even guix pulling, > > I need to add the subsitute option for using https://ci.guix.info > > Otherwhise it uses the mirror from hydra. > > That's weird... Yes, it is quite strange > > Is your guix-daemon also recent? > > Try: > > /proc/$(pidof -s guix-daemon)/exe -V > > in order to find out its version. What does it say? Weirdest, look at this: guix-daemon (GNU Guix) 0.16.0-3.6ddc63e root@ada:~# /proc/$(pidof -s guix-daemon)/exe -V guix-daemon (GNU Guix) 0.15.0-8.71a78ba > > Does your system configuration in /etc/config.scm specify custom > substitute-urls ? I don't have that file? should I? Regards :) Laura
Re: Patchwork + automated checking and testing of patches
On Fri, 08 Feb 2019 12:04:20 + Christopher Baines wrote: > Thanks, however, one thing I've noticed is that git apply seems to be > much more reliable at applying patches than git am. It often fails > with "Patch is empty". > > I'm not sure why, it seems to work for the patches I've sent with git > send-email, but maybe it's very particular about the formatting... Maybe you already thought about it, but: When I use it manually, I save the whole patch-series as an mbox-file, including the "--cover-letter", i.e. the first email saying [0/n]. When I then say "git am patch.mbox" it complains there is nothing in. I then have to say "git am --skip" and it goes on automatically. Could that also be the case with your patchwork-setup? Björn pgpKgl0qs4iHl.pgp Description: OpenPGP digital signature
Re: Inverting command line session colours
Hello Laura, > I am having trouble inverting the colours of the command line session > videos. They should be black in the foreground with white text. > Gábor, I guess you solved that, could you remind me how you did it? > There was a link with -negate in convert but did not work for me. > Here is a command that works for me: convert xyz.ps -background white -flatten -negate xyz.png > Regards :) > Laura Best regards, g_bor
Re: New videos: topic daily use.
Björn Höfling writes: > On Wed, 06 Feb 2019 23:17:21 +0100 > Ricardo Wurmus wrote: [...] >> Sounds good. “--install”, “--roll-back”, and maybe even “--manifest” >> for stateless installations would be good topics to cover. > > Is "--manifest" really "daily use" for a Guix newbie? it *should* be, it's strongly advised: using manifests has a _very_ little learning curve, it's a **huge** enhancement at a very little cost; every Guix user *must* know this from the very beginning at first a newbie *could* not fully understand and appreciate this, but this distinguishing feature must stimulate each and every newbie to understand the underling concept of declarative stateless installation ...aka: Guix is very smart as a package manager (with rollbacks too!), but it'm much more than a package manager ...just my two cents :-) [...] Thanks! Giovanni -- Giovanni Biscuolo Xelera IT Infrastructures signature.asc Description: PGP signature
Re: New videos: topic daily use.
Björn Höfling writes: >> > I was thinking of daily use of guix package, mentioning profile, >> > generations (both the concepts and commands to deal with them) >> >> Sounds good. “--install”, “--roll-back”, and maybe even “--manifest” >> for stateless installations would be good topics to cover. > > Is "--manifest" really "daily use" for a Guix newbie? I would disagree > and first stick to the "--install" --"remove "--rollback" > "--list-generations" mode. You’re probably right. I keep recommending the use of manifests here at work, but I suppose this could be explained in another video (with a focus on reproducibility maybe). -- Ricardo
Re: ‘nss-certs’ missing in the installation image
Pierre Neidhardt skribis: > From 082f569611a889ef0e852263b5ba23373936b422 Mon Sep 17 00:00:00 2001 > From: Pierre Neidhardt > Date: Fri, 8 Feb 2019 15:30:08 +0100 > Subject: [PATCH] install: Add nss-certs to the image. > > * gnu/system/install.scm (installation-os)[packages]: Add nss-certs. LGTM, thanks! Ludo'.
Re: libgtk3-nocsd and LD_PRELOAD
Hello Björn!
Björn Höfling skribis:
> I'm using Guix on top of Ubuntu. Error appears when using programs
> installed from Guix. After some investigations, I found out this
> environment variable is set in:
>
> /etc/X11/Xsession.d/51gtk3-nocsd-detect
>
> *)
> # not GNOME, and the user didn't specify GTK_CSD
> # themselves, so set it to 0
> if [ -z "$GTK_CSD" ] ; then
> GTK_CSD=0
> fi
> export GTK_CSD
> if [ x"$GTK_CSD"x = x"0"x ] ; then
> export
> LD_PRELOAD="libgtk3-nocsd.so.0${LD_PRELOAD:+:$LD_PRE fi
> ;;
>
> I'm currently using a non-GNOME windowing environment, so I'm in this case.
>
> The library is this:
>
> https://github.com/PCMan/gtk3-nocsd
>
> It should make some things nicer if you don't use GNOME. This seams to
> be a hack. Do we need this library in Guix too, to get some decorations
> back?
Regardless of what this library does, if you need to preload it for
Guix-built applications, then this library should also be built from
Guix (otherwise you end up with several libcs, etc. in the same process,
which is never a good thing.)
So I’d recommend packaging this library and then you can hopefully
preload at will. :-)
HTH!
Ludo’.
Re: Merging ‘wip-newt-installer’ in master?
Pierre Neidhardt skribis: > I confirm that the RX580 does not have framebuffer/KMS support with the ATI > driver. > There is KMS support with the AMDGPU driver, sadly it requires some > proprietary > blob :( I’d expect the framebuffer to always work, at least through VESA, no? > During the Guix days you mentioned that you went for KMSCON because of > encoding > issues if I recall correctly. So what about this: on startup, test if KMS is > supported. If not, fall back to the default TTY, and too bad for the limited > encoding :p Would that work? That would be a reasonable workaround. Ludo’.
Re: Inverting command line session colours
Hi! > convert xyz.ps -background white -flatten -negate xyz.png I had already tried the -negate before but didn't work, I only got full white pngs (the text turned white) I am running imagemagick6.9.10-14 this is the rule: -starts (VIDEO)/$(LOCALE_LANG)/out/$(SESSION)-%.png: $(VIDEO)/$(LOCALE_LANG)/out/$(SESSION)-%.txt tail -n 20 $< | \ paps --landscape --columns=80 --font "Monospace 20" | \ convert -density 128 \ -fill black \ -background white \ -flatten \ -rotate 90 \ -delete 0--2 - $@ ---ends---
Re: New videos: topic daily use.
On 2019-02-08 18:43, Ricardo Wurmus wrote: Björn Höfling writes: > I was thinking of daily use of guix package, mentioning profile, > generations (both the concepts and commands to deal with them) Sounds good. “--install”, “--roll-back”, and maybe even “--manifest” for stateless installations would be good topics to cover. Is "--manifest" really "daily use" for a Guix newbie? I would disagree and first stick to the "--install" --"remove "--rollback" "--list-generations" mode. You’re probably right. I keep recommending the use of manifests here at work, but I suppose this could be explained in another video (with a focus on reproducibility maybe). I am also looking for a video about manifests. -- Amirouche ~ amz3 ~ http://www.hyperdev.fr
Re: Inverting command line session colours
Hi Laura, this kept me awake, I had to open my laptop again :-) On Fri, 8 Feb 2019 19:53:50 -0300 Laura Lazzati wrote: > Hi! > > convert xyz.ps -background white -flatten -negate xyz.png > I had already tried the -negate before but didn't work, I only got > full white pngs (the text turned white) > I am running imagemagick6.9.10-14 this is the rule: > -starts > (VIDEO)/$(LOCALE_LANG)/out/$(SESSION)-%.png: > $(VIDEO)/$(LOCALE_LANG)/out/$(SESSION)-%.txt > tail -n 20 $< | \ > paps --landscape --columns=80 --font "Monospace 20" | \ > convert -density 128 \ > -fill black \ > -background white \ > -flatten \ > -rotate 90 \ > -delete 0--2 - $@ > ---ends--- I can confirm this problem, let's track it down the Guix way: ## Make sure we are really talking about the same, getting into a fresh container of latest guix: # To make sure you are at the same commit where I tested this, you could do a: $ guix pull --commit=307182d4f7b1a56e220f208ad5f886e7784db115 $ guix describe Generation 46 Feb 08 2019 23:58:31(current) [.. other channels here ..] guix 307182d repository URL: https://git.savannah.gnu.org/git/guix.git branch: master commit: 307182d4f7b1a56e220f208ad5f886e7784db115 $ cd /tmp $ mkdir tst $ cd tst # really get into a container, to be extra sure! /tmp/tst$ guix environment -C --ad-hoc coreutils less imagemagick paps $ convert -version Version: ImageMagick 6.9.10-14 Q16 x86_64 2018-11-14 https://imagemagick.org Copyright: © 1999-2018 ImageMagick Studio LLC License: https://imagemagick.org/script/license.php Features: Cipher DPC OpenMP Delegates (built-in): bzlib fftw fontconfig freetype gvc jng jpeg lcms lzma pangocairo png tiff x xml zlib # Create a postscript file we can work with: $ echo "Hello, World!" | paps --landscape --columns=80 --font "Monospace 20" > hello-world.ps # This output looks good, white background, black text: cat hello-world.ps| convert -density 128 -fill black -background white -flatten -rotate 90 -delete 0--2 - out.png # Though I'm getting this warning, is that the problem?: # convert: profile 'icc': 'RGB ': RGB color space not permitted on grayscale PNG `out.png' @ warning/png.c/MagickPNGWarningHandler/1667. # This produces only whiteness: # Same warning as above: cat hello-world.ps| convert -density 128 -fill black -background white -flatten -rotate 90 -delete 0--2 -negate - out-negated.png #But at least this works afterwards: White text on black background: convert out.png -negate outout.png Conclusion: As a quick workaround, you can add another pipe and use convert twice. But there should be a way to do it in one way. ImageMagick is a bit tricky in that. I have no idea for now. As reference, I'm attaching my output files. Björn hello-world.ps Description: PostScript document pgpIAijBqwPWK.pgp Description: OpenPGP digital signature
Re: Inverting command line session colours
Go to bed Bruno :) I will be writing another mail, and answer back this one. but go to bed! your intern will tell Sage, you have to recover from your cold. On Fri, Feb 8, 2019 at 8:44 PM Björn Höfling wrote: > > Hi Laura, > > this kept me awake, I had to open my laptop again :-) > > On Fri, 8 Feb 2019 19:53:50 -0300 > Laura Lazzati wrote: > > > Hi! > > > convert xyz.ps -background white -flatten -negate xyz.png > > I had already tried the -negate before but didn't work, I only got > > full white pngs (the text turned white) > > I am running imagemagick6.9.10-14 this is the rule: > > -starts > > (VIDEO)/$(LOCALE_LANG)/out/$(SESSION)-%.png: > > $(VIDEO)/$(LOCALE_LANG)/out/$(SESSION)-%.txt > > tail -n 20 $< | \ > > paps --landscape --columns=80 --font "Monospace 20" | \ > > convert -density 128 \ > > -fill black \ > > -background white \ > > -flatten \ > > -rotate 90 \ > > -delete 0--2 - $@ > > ---ends--- > > I can confirm this problem, let's track it down the Guix way: > > ## Make sure we are really talking about the same, getting into a fresh > container of latest guix: > > # To make sure you are at the same commit where I tested this, you > could do a: > $ guix pull --commit=307182d4f7b1a56e220f208ad5f886e7784db115 > > $ guix describe > Generation 46 Feb 08 2019 23:58:31(current) > [.. other channels here ..] > guix 307182d > repository URL: https://git.savannah.gnu.org/git/guix.git > branch: master > commit: 307182d4f7b1a56e220f208ad5f886e7784db115 > > $ cd /tmp > $ mkdir tst > $ cd tst > # really get into a container, to be extra sure! > /tmp/tst$ guix environment -C --ad-hoc coreutils less imagemagick paps > > $ convert -version > Version: ImageMagick 6.9.10-14 Q16 x86_64 2018-11-14 https://imagemagick.org > Copyright: © 1999-2018 ImageMagick Studio LLC > License: https://imagemagick.org/script/license.php > Features: Cipher DPC OpenMP > Delegates (built-in): bzlib fftw fontconfig freetype gvc jng jpeg lcms lzma > pangocairo png tiff x xml zlib > > # Create a postscript file we can work with: > $ echo "Hello, World!" | paps --landscape --columns=80 --font "Monospace 20" > > hello-world.ps > > # This output looks good, white background, black text: > cat hello-world.ps| convert -density 128 -fill black -background white > -flatten -rotate 90 -delete 0--2 - out.png > > # Though I'm getting this warning, is that the problem?: > # convert: profile 'icc': 'RGB ': RGB color space not permitted on grayscale > PNG `out.png' @ warning/png.c/MagickPNGWarningHandler/1667. > > # This produces only whiteness: > # Same warning as above: > cat hello-world.ps| convert -density 128 -fill black -background white > -flatten -rotate 90 -delete 0--2 -negate - out-negated.png > > #But at least this works afterwards: White text on black background: > convert out.png -negate outout.png > > > > Conclusion: As a quick workaround, you can add another pipe and use > convert twice. > > But there should be a way to do it in one way. ImageMagick is a bit > tricky in that. I have no idea for now. > > As reference, I'm attaching my output files. > > Björn >
What is guix.info?
Hi, I'm planning to do some more work on the Guix website, and found out that there is a new instance in guix.info. Could you tell me a little bit more about it, please (who runs it, how it gets updated, ...)? I couldn't find much information in the archives. Thanks, -- Luis Felipe López Acevedo http://sirgazil.bitbucket.io/
