Re: Non-bootstrappable NPM packages

Heyo, Nicolas Graves writes: > Did someone made some progress on the build-system since that to allow > for this to be taken into account? If you still have it, could you share > your "fiio" packages once again? The paste link is expired. Thanks! To my knowledge (it’s two years old now, so mayb

Re: Preservation of Guix report for 2024-01-26

Ludovic Courtès writes: > Thumbs up on bzip2 support! We should update Disarchive in Guix but > perhaps that’s already in your pipeline? I sent https://issues.guix.gnu.org/68769. Now I see that I didn’t have the newest Git hooks installed, so no change ID and no email to the relevant team. So

Preservation of Guix report for 2024-01-26

Hello all, For a while now, I’ve been tracking coverage of Guix sources in the Software Heritage (SWH) archive. I maintain a dataset of sources that goes back (almost five years) to Guix 1.0.0. Every once in a while, I update this dataset and check it against SWH to see how much is missing. I ju

Re: Git-LFS or Git Annex?

Simon Tournier writes: >> Special remotes can also be written in other languages: >> >> https://git-annex.branchable.com/design/external_special_remote_protocol/ > > Thanks! I did not know. Indeed, it could be a nice GSoC to implement > some ‘git-annex-backend-nar’. :-) I’ve written a specia

Re: [swh-devel] Call for public review - SWH Nix/GNU Guix stack

Hello, This is very exciting work, thanks everyone! "Antoine R. Dumont (@ardumont)" writes: > FWIW, in the "new" lister [1] implementation, there are a bunch of extra > computations done [1] to try and resolve those situations. It's trying > to fetch more information from upstream server (e.g.

Re: Adding GNAT/GCC-Ada to Guix

r Ada 95, too, but I can’t remember if it is freely licensed. It could be used to bridge the gap between Ada-Ed and old GNAT (maybe). -- Tim ;;; Copyright © 2018 Timothy Sample ;;; SPDX-License-Identifier: GPL-3.0-or-later (use-modules (gnu packages bootstrap) (gnu packages elf)

Re: Guix meetup at FOSSY?

Hi, Vagrant Cascadian writes: > My current best idea is the handful of food carts at pioneer courthouse > square, with a few different carts that cater to various dietary needs > and appetites... about 10-15 minutes on the MAX, with stops right at > both endpoints! This sounds great, but I just

Re: Guix meetup at FOSSY?

Vagrant Cascadian writes: > On 2023-07-04, Timothy Sample wrote: > >> What about having a Guix lunch on Friday? I don’t really have strong >> feelings, but I thought I’d propose something concrete to get things >> going. I’ve never been to Portland, so I don’t have th

Re: Guix meetup at FOSSY?

Vagrant Cascadian writes: > On 2023-06-29, Timothy Sample wrote: >> The first FOSSY (Free and Open Source [Software] Yearly) conference >> is coming up in two weeks! It’s being hosted in Portland, OR by the >> Software Freedom Conservancy. >> >> Why d

Guix meetup at FOSSY?

Hi all, The first FOSSY (Free and Open Source Yearly) conference is coming up in two weeks! It’s being hosted in Portland, OR by the Software Freedom Conservancy. I was looking over the schedule and I spotted a few familiar names from the Guix community. Why don’t we plan a little Guix meetup?

Re: Welcome to Simon as a new committer

Maxim Cournoyer writes: > I'd like to welcome Simon (aka zimoun) as a new committer. They have > made many contributions along the years, both in code and in community > management. For sure! Congrats, Simon, and thank you for all your hard work. :) -- Tim

Re: disarchive: disassemble then assemble tarball

Hi Simon, Simon Tournier writes: > Discussing in #62153 [1], it is noticed that Disarchive is not working > as expected. To be fair, Oleg is experimenting with reusing some internal Disarchive code in another context. That experiment didn’t go well, and Oleg came to a good (IMO) conclusion: tr

Re: Preservation of Guix (PoG) report 2023-03-13

Hi Ludo, Ludovic Courtès writes: > Do you think this could be turned into a Guix System service, with an > eye towards making it run on project infrastructure? I need to revisit what you did with Disarchive and Cuirass. The process for the PoG report is very similar. I can’t jump into it righ

Re: Preservation of Guix (PoG) report 2023-03-13

Hey, Simon Tournier writes: > Well, I do not remember if you consider also the ’origin’ > (fixed-outputs) as ’inputs’ or ’patches’. Do you? I’m quite confident I’m getting everything. I’ll describe my approach, because I’m happy with it. :) The Guix package graph exists twice, essentially.

Re: Disarchive database synchronization

Hey Ludo, Ludovic Courtès writes: > I copied over the 12K entries that were missing from > disarchive.guix.gnu.org. (Note that there are currently only two copies > of the database: one at/in [bB]erlin, and one at/in [Bb]ordeaux.) > disarchive.guix.gnu.org now weighs in at 1.8 GiB for 31,839 en

Preservation of Guix (PoG) report 2023-03-13

b/Archive/DiffBind/ [3] https://bioconductor.org/packages/3.10/bioc/html/ggcyto.html That’s all for now. Enjoy the update and the script! -- Tim ;;; specification-to-swhids.scm ;;; Copyright © 2023 Timothy Sample ;;; ;;; This program is free software: you can redistribute it and/or modify ;;; it

Re: GNU Guix on iPad2 (A1395)

Hi Jacob, Jacob Hrbek writes: > The issue is that i can't get libusbmuxd (the daemon used to > communicate with iDevices from Linux) to work on GNU Guix likely due > to a configuration error in guix to perform the exploit and install > guix, can someone help? > https://github.com/libimobiledevic

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

Hi Konrad, Ludovic Courtès writes: > Konrad Hinsen skribis: > >> The package I want to rebuild and use is "nmoldyn" from Guix commit >> f250a868d8c687df08559682fa68fb4ea2a1ea69. That's the commit referenced >> in my notes, obtained via "guix describe" in early 2018. I am pretty >> sure it worke

Re: Unable to bootstrap Guix without substitutes

Hi Greg, Greg Hogan writes: > When installing the Guix binary distribution (both the 1.3.0 release > and most recent guix-binary on ci.guix.gnu.org) on a new system > without enabling substitutes the guix pull or install commands fail > when building bash-mesboot0. > > [...] > > The error from t

Re: missing patch for texlive-bin (e77412362f)

Hi, zimoun writes: > On Thu, 03 Feb 2022 at 10:46, Timothy Sample wrote: > >> The bad news is that 0.75 is not there. At first I was going to >> apologize for the shortcomings of the sampling approach... until I >> realized you are trying to trick me! ;) Unles

Re: missing patch for texlive-bin (e77412362f)

Hi zimoun, zimoun writes: > But the question is if Disarchive dissambles and preserves external > patches. Timothy? I have good news and bad news. :) The good news is that some versions of this patch are in the PoG database. There’s two versions of 0.76 and one of 0.72. Of those three, onl

Re: ImageMagick from 2020?

Hey, zimoun writes: > On Wed, 19 Jan 2022 at 11:36, Ludovic Courtès wrote: > >> Oh right, so we’ll need to feed them historical ‘sources.json’ files >> eventually, I think Timothy was planning to do that eventually. > > From my side, what I would like to achieve soon: > > [...] > > Then what is

Re: Preservation of Guix report 2022-01-16

Hi, Vagrant Cascadian writes: > On 2022-01-18, Ludovic Courtès wrote: >> Timothy Sample skribis: >>> A really important thing to do at this point is to verify that some >>> reasonable looking computation is covered by what we are doing already. >>> For ins

Preservation of Guix report 2022-01-16

Hi all, I’ve published a new preservation of Guix report: https://ngyro.com/pog-reports/latest/ Actually, the URL is , but I thought having a way to reference the latest report would be helpful. There’s no big news in the report. I’ve tracked down

Re: ImageMagick from 2020?

Hi zimoun, zimoun writes: > We probably do not have this item. Since it is 'xz', it is somehow > expected because it is works in progress. XZ support is working in Disarchive now. I’m hosting quite a few XZ specifications at . > Can someone confirm we do not eff

Re: On raw strings in commit field

em 01.01.2022 um 12:45 -0500 schrieb Timothy Sample: > >> Given what I wrote above, maybe we could start by updating the linter >> so that ‘check-source’ actually checks that it gets the right result. >> Right now it uses a few heuristics to check that the result looks >> ok

Re: On raw strings in commit field

Hi all, Liliana Marie Prikler writes: > Am Freitag, dem 31.12.2021 um 20:41 -0500 schrieb Mark H Weaver: > >> If upstream later indicates that version "1.2.3" is now commit YYZ, I >> don't think that invalidates our basis for continuing to associate >> version "1.2.3" with commit XYZ.  The afore

Re: core-updates-frozen branch merged

Hi Maxim, Maxim Cournoyer writes: > In case you hadn't taken notice, the core-update-frozen branch was > finally merged into master. So please reconfigure your remotes to avoid > uploading any further work there :-). > > [...] > > That's it! Enjoy the latest additions and improvements, and rep

Preservation of Guix Report 2021-12-06

Hi Guix, This is an update to the preservation of Guix report. There are no new commits or fixed-output derivations in this report, but I spent some time cleaning up the results, and I think the improvements are worth sharing. The last report generated a lot of questions. This one doesn’t answe

Re: How to compute SWHID? (with Guix/Disarchive)

Hi, Ludovic Courtès writes: > zimoun skribis: > >> Giving a look at Disarchive, I found how to compute Git-based >> serialization hash and somehow serialization methods of "guix hash" >> needs some clearning; considering '--recursive' is 'nar' serialization >> which is a better name. Anyway, s

Re: [core-updates-frozen] Haskell for i686-linux: report

Hi, zimoun writes: > After some Cuirass monitoring and restarted some unexpected failures, > the situation for ghc-* on i686-linux is the same as the one from > current master. I took a few minutes to triage these. Most of them are fixable. > Two packages are broken in core-updates-frozen and

Re: Preservation of Guix Report 2021-11-30

Timothy Sample writes: > [W]e are starting to lose sources! If you look at the graph of > commits, you can see a sharp increase in missing sources for recent > commits. It looks like a problem on the SWH side. Visiting [1] and > selecting “Show all visits”, you can see that the ni

Re: Software Heritage fifth anniversary event

Hi, zimoun writes: > Timothy, could you provide again the entry point you use? https://docs.softwareheritage.org/devel/swh-web/uri-scheme-api.html#post--api-1-known- -- Tim

Preservation of Guix Report 2021-11-30

Hi Guix! Here’s a new version of the Preservation of Guix Report: I actually made one a month ago but my message about it never made it to the list somehow. The most important part of that message was to highlight how well we are doing for Git sou

Re: Software Heritage fifth anniversary event

Ludovic Courtès writes: > I gave a 10–15mn talk on how Guix uses SWH, what Disarchive is, what > the current status of the “preservation of Guix” is, and what remains > to be done: > > > https://git.savannah.gnu.org/cgit/guix/maintenance.git/plain/talks/swh-unesco-2021/talk.20211130.pdf Wow –

Re: Preservation of Guix 2021-10-22

Hi zimoun, zimoun writes: >>> How can I get the list of these 376+217 packages? Because it appears to >>> me easy to send a save request for them. :-) > > Done. :-) Nice! > I have not checked one per one but I guess the 217 are included in the > 376 ones. As I said earlier, many of them are

Re: Preservation of Guix 2021-10-22

Hello, zimoun writes: > How can I get the list of these 376+217 packages? Because it appears to > me easy to send a save request for them. :_) Download the database (there’s a button at the bottom of the report), and use SQLite to run the following queries. For the 376: SELECT fod_id,

Preservation of Guix 2021-10-22

Hey all, As promised, here is the updated Preservation of Guix Report: https://ngyro.com/pog-reports/2021-10-22/ It takes into account the as yet unreleased Disarchive fix. The results are quite a bit better! Note especially that for the most recent commit, of the 72.8% that I could check,

Re: Preservation of Guix Report

Hi again, Timothy Sample writes: > Yes, but I have another trick. The “known” endpoint [1]. If you > already know the SWHIDs you want to check, you can check 1,000 per call. > With the anonymous rate limit, I can check 120,000 every hour, which is > plenty. >

Re: Preservation of Guix Report

Hey, Ludovic Courtès writes: > Timothy Sample skribis: > >> Early this summer I did a bunch of work trying to figure out which Guix >> sources are preserved by the SWH archive. I’m finally ready to share >> some preliminary results! >> >> http

Re: Preservation of Guix Report

Hi zimoun, zimoun writes: > 2. For still unknown reasons, the bridge between SWH and Disarchive has > some holes. For instance, > > $ guix lint -c archive znc > gnu/packages/messaging.scm:996:12: znc@1.8.2: Disarchive entry refers > to non-existent SWH directory '33a3b509b

Re: Preservation of Guix Report

Hi again, Rereading this a few hours later, I found an error. Timothy Sample writes: > It’s surprising to me that SWH is not already getting these from > “sources.json”. I picked an arbitrary one, “rust-quote-0.6”, and it’s > simply not in “sources.json”. It is in fact there!

Preservation of Guix Report

Hi everyone! Early this summer I did a bunch of work trying to figure out which Guix sources are preserved by the SWH archive. I’m finally ready to share some preliminary results! https://ngyro.com/pog-reports/2021-10-20/ This report is already quite outdated, though. It only covers commit

Re: Disarchive update

! I feel bad that I left you holding the bag on this one, though. Sorry. I’ve been a little adrift this summer. Thanks for picking it up! > Where to go from here? Timothy Sample had already set up a Disarchive > database at <https://disarchive.ngyro.com>, which (guix download) uses

Re: Will 2021 be the year of build systems on gexps?

Hi Ludo, Ludovic Courtès writes: > So this is it, 2021 *is* the year of build systems on gexps! Wow! Congratulations! I am very happy to see this finally come together. > It’s crazy that it took 6 years (six!) to get past the finish line. I think I’ve only known what a gexp is for three yea

Re: wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello'

Hi janneke, Jan Nieuwenhuizen writes: > I have reset Guix' wip-full-source-bootstrap branch with a first working > implementation of the, well, "Full Source Bootstrap" for x86-linux (and > x86_64-linux). This bootstrap is rooted in the 357-byte hex0-seed from > the Stage0 project (https://savan

Re: Guile 2.0 in make-bootstrap.scm

Hi all, Jan Nieuwenhuizen writes: >> What’s surprising is that >> does use >> 2.2. > > Oh, that's weird. Well, we used gule-2.2 until almost the very last > moment, I remember. I am cc'ing Timothy, as he helped make the > guile-2.0 b

Re: Etymology of derivation

Hello, Ludovic Courtès writes: > Arun Isaac skribis: > >> The original Nix publication was helpful. On page 22 of the full thesis, >> it says: >> >> Derivation is Nix-speak for a component build action, which derives >> the component from its inputs. > > Not sure if it helps, but I struggled a

Re: merge wip-haskell?

Hi again, Timothy Sample writes: > I‘ll take a look at PureScript and check Elm, since maybe the Agda fix > will work for them. I’m not sure about Idris – it needs a bit more > effort. Good news! Elm and PureScript are fine, and I just pushed a fix

Re: merge wip-haskell?

Hi John, John Soo writes: > Does anyone know why idris, agda, and purescript are failing? The really short version is that we now use shared libraries for Haskell dependencies, which mostly works, except for some of the more complicated builds. I did fix Agda a little while ago, so I think it’

Re: merge wip-haskell?

Hey Ricardo, Ricardo Wurmus writes: > Ricardo Wurmus writes: > >> Timothy Sample writes: >> >>> I just pushed “wip-haskell-updates-2” which integrates my work from >>> <https://issues.guix.gnu.org/39309>. I left the original branch intact >>&g

Re: merge wip-haskell?

Hi Ricardo, Ricardo Wurmus writes: > Timothy Sample writes: > >> Also, it looks like “wip-haskell-updates” is no longer being built by >> the CI infrastructure. Since the branch triggers a rebuild of all the >> Haskell packages, it should be built before merging, rig

Re: merge wip-haskell?

Hi John and Ricardo, John Soo writes: > I believe there was also some work being done to de-duplicate flags > sent to gcc sent by ghc (this was the only thing keeping stack from > building). > I hope that can make it in, too! I agree, and sorry to you John for the delay. I’m not using much Has

Re: “Grafts, continued”

Hello, What an interesting read. Well done, Ludo! Nicolò Balzarotti writes: > Interesting blog post, thanks! > I found a typo: > /remove-eval/remote-eval/ Me too: s/more of hint/more of a hint/ -- Tim

Re: core-updates call for testing

Hi Marius, Marius Bakke writes: > The "core-updates" branch is ready for testing! [...] > > Please try upgrading your profiles and systems and file bugs for > anything that does not work for you. GNOME users in particular are > encouraged to try the new GNOME 3.34 and report any regressions.

Re: Bump stackage LTS

Hi, Timothy Sample writes: > AFAIK, we are OK to use the wip-haskell branch. I will reset it to > master and get started today or tomorrow. I just pushed GHC 8.8 to wip-haskell-updates, which I reset to core-updates. (I’m betting that core-updates will be merged before the Haskell u

Re: Bump stackage LTS

Hi John, I’m just catching up on the list after a long hiatus, so sorry for the wait. John Soo writes: > Hi Guix, > > Stackage and ghc have moved quite a bit since our stackage and ghc > versions. Would it be ok to start work on bumping our package set to > a newer set of working packages and

Re: 05/05: gnu: Add ghc-hspec-discover.

Hi, Nicolas Goaziou writes: > > Timothy Sample writes: > >> We already have “hspec-discover” without the “ghc” prefix. The two >> packages look identical to me – is this an unintentional copy? > > Oh! I hadn't noticed! > > Well, is there any strong reas

Re: 05/05: gnu: Add ghc-hspec-discover.

Hi Nicolas, guix-comm...@gnu.org writes: > ngz pushed a commit to branch master > in repository guix. > > commit a60448edcc85faa8b3cd4bd3ae8a336c842aad4d > Author: Nicolas Goaziou > AuthorDate: Sat Feb 8 15:17:15 2020 +0100 > > gnu: Add ghc-hspec-discover. > > * gnu/packages/haskell

Re: Error while packaging Stack

Hi John, John Soo writes: > I'm working on packaging Stack and have all the dependencies. > > When I try to package stack itself, I get the following error: > > gcc: error trying to exec > '/gnu/store/...-gcc-7.4.0/libexec/gcc/x86_64-unknown-linux-gnu/7.4.0/collect2': > execv: Argument list too

[ANN] Gash 0.2.0 released

Hi everybody, I am very pleased to announce that Gash version 0.2.0 has been released. It represents 58 commits from two authors over the course of about six months. About = Gash is a POSIX-compatible shell written in Guile Scheme. It provides both the shell interface, as well as a Guile li

Re: Feedback from JRES in Dijon

Hi Bengt, I omitted a lot of your message, but I hope I have the easy explanation you’re looking for. :) Bengt Richter writes: > On +2019-12-07 11:35:02 -0500, Timothy Sample wrote: >> >> [...] >> >> Unfortunately, I got certificate errors, but VLC lets you

Re: Feedback from JRES in Dijon

Hello, Konrad Hinsen writes: > Hi Bengt, > >>> [1] >>> https://webcast.in2p3.fr/video/les-enjeux-et-defis-de-la-recherche-reproductible >>> https://aramis.resinfo.org/wiki/lib/exe/fetch.php?media=pleniaires:aramis_keynote_enjeux-et-defis-recherche-reproductible_konrad_hinsen.pdf >>> >> >> Is [1]

Re: Status of Gnome upgrade?

Hi all, I’ve CC’d Kei who has been looking after this. Thanks Kei! Brett Gilio writes: > Ricardo Wurmus writes: > >> Hi Guix, >> >> does anyone know what’s holding up the Gnome upgrade? It’s sad to see >> the upgrade languish when it was almost ready for a merge into master. >> >> Are there

Re: Package inputs in manifests

Hi Bengt, Bengt Richter writes: > On +2019-11-23 15:05:49 +0100, Ludovic Courtès wrote: >> >> Bengt Richter skribis: >> >> > Can "collisions" be collisions even if the targets are bit-identical? >> >> Collisions are when the same package appears several times with >> different version string

Re: Stackage LTS 14

Hi Marius, Marius Bakke writes: > I appreciate the heads-up. Thanks again for taking on this task. The > branch LGTM. > > I've restarted the builds that you mentioned in another message. How is > the weather looking, do you think it's ready to merge? :-) There are a few remaining issues, bu

Re: Stackage LTS 14

Hi again, Timothy Sample writes: > Marius Bakke writes: > >> I've read some of the changes and they LGTM. If Cuirass is happy, I >> think you can go ahead and merge the branch. \o/ > > I just put everything together and rebased it all on master, fixing > se

Re: Stackage LTS 14

Hi, Marius Bakke writes: > I've read some of the changes and they LGTM. If Cuirass is happy, I > think you can go ahead and merge the branch. \o/ I just put everything together and rebased it all on master, fixing several typos as I did so. :) It seems that “ghc@8.6.5” has changed a few day

Re: Stackage LTS 14

Hi John, John Soo writes: > When we bump to Stackage 14 can issue 36653 be closed? I think these changes should still be merged (with review and fixes). Eventually Stackage LTS 15 will come out while we’re still on LTS 14. At that point, we will have the same issue with the importer and linter

Re: Stackage LTS 14

Hi John, John Soo writes: > Xmobar builds properly with all the extensions but I haven't really given it > a spin. I did have to > add a few more packages, but I think they are reasonable. This is fantastic! Thanks so much for your help. > I think the update to ghc after 8.4 will fix a segf

Re: Stackage LTS 14

Hi John, John Soo writes: > Thanks for putting in the work. I use xmobar with a few extra options: > dbus, alsa and maybe one more. I can’t remember. I can try submitting > a patch for it this week. Hooray! If I fix “ngless” this will be pretty much ready to merge. Then (pause while a short fa

Re: Stackage LTS 14

Hi again, Timothy Sample writes: > However, I have a really weird problem. When I build “git-annex”, I > build > > /gnu/store/5i2x293qn45dwg2rv6vy45s0r9jbnv8l-git-annex-7.20191024.drv > > and it succeeds. On the build farm, it’s > > /gnu/store/fj5kyjkblxzc

Re: Stackage LTS 14

Hello, Timothy Sample writes: > I have “xmonad”, “darcs”, “ghc-pandoc”, and “git-annex” all building > (locally) on top of GHC 8.6, which means that we’re nearly there. > Unfortunately, the mess is getting to be too much, so I plan to clean it > up tomorrow and then push a new, cle

Re: 'core-updates' Q4 2019

Hi Kei, Kei Kebreau writes: > `git push --force-with-lease` doesn't seem to work on the WIP branch. > This is a good thing in general, but how do I rewrite history? Do I > just delete the remote WIP branch and recreate a new one with the > appropriate changes? Yup! This is what I do for “wip-h

Re: GDM and Wayland

Hi Raghav, Raghav Gururajan writes: > Hello Guix! > > When I was reviewing guix manual, it was mentioned that only gnome has > support for wayland. > > I was wondering why gdm is not showing option to start gnome session > using wayland? gdm is part of gnome correct? Yes it is, but GNOME was wo

Re: Stackage LTS 14

Hi all, Timothy Sample writes: >> Ricardo Wurmus writes: >> >>> Yes, you can take over wip-haskell-updates. > > Great! I’ve pushed a new branch with updated Haskell packages. It’s a > little messy yet, but I want the build farm to help me find build > problem

Re: Stackage LTS 14

Hello, Marius Bakke writes: > Ricardo Wurmus writes: > >>> Ricardo, what do you think? Are we okay to take over >>> wip-haskell-updates? Does a mega commit make sense or do you think >>> that’s a bad idea? >> >> Yes, you can take over wip-haskell-updates. Great! I’ve pushed a new branch wit

Re: 'core-updates' Q4 2019

Hi Marius, Marius Bakke writes: > LGTM. It needs a corresponding entry in doc/guix.texi though. Pushed with an update to the docs. Thanks for the suggestion and review! -- Tim

Re: 'core-updates' Q4 2019

Hi Marius, Marius Bakke writes: > Timothy Sample writes: > >> [1] It’s not obvious, but if you edit the GDM configuration file >> generation code in “gnu/services/xorg.scm”, you can enable debug output >> for GDM. The debug output is usually extremely helpful! > &

Re: 'core-updates' Q4 2019

Hi again, Timothy Sample writes: > I’ll report back if I have good luck with fsck and am able to do more > testing. :) I was able to build everything and start testing. To use “guix system vm” I had to disable tests in QEMU due to a failure. I did not investigate it. This turned up

Re: 'core-updates' Q4 2019

Hi Kei and Florian, "pelzflorian (Florian Pelz)" writes: > On Sat, Oct 19, 2019 at 11:29:33PM -0400, Kei Kebreau wrote: >> I've pushed my changes to the following repository for anyone who wants >> to take a look: >> >> https://notabug.org/kei/guix-gnome-updates > > I tried reproducing your fai

Stackage LTS 14 (was: Adding Purescript)

Hi John, John Soo writes: > I have packaged PureScript in a channel and I would like to merge it Cool! > Some of its dependencies are from hackage and are much newer than > those in the stackage snapshot we use. So my question is where should > the dependencies belong? Maybe we should just b

Re: 'core-updates' Q4 2019

Hi Kei, Kei Kebreau writes: > Anyone want to see the 54 patches and possibly help me root around for > the issue? I would love to take a look at it! I’ve been a little tied up, but I should have some time tomorrow or the next day. I think it would be easiest to push it to some world-readable

Re: DE

Hello, guixest writes: > I understand the process you explained. Btw, when is the next batch coming? Marius suggested that we start working on it soon and try to finish it in December: https://lists.gnu.org/archive/html/guix-devel/2019-10/msg00108.html -- Tim

Re: DE

Hi guixest, guixest writes: > hi. > I was looking at available gtk based desktops. It appears xfce is up to date > where as gnome > is not. is there a reason for this? Yes and no. As I understand it, upgrading GNOME often means upgrading GTK and GLib, which have a lot of dependants. We batch

Re: 01/01: gnu: cedille: Adjust import list.

Hi Ludo, guix-comm...@gnu.org writes: > civodul pushed a commit to branch master > in repository guix. > > commit aa0f683462fd66630c0731f09275e14c9dfe0118 > Author: Ludovic Courtès > Date: Sun Sep 1 00:11:17 2019 +0200 > > gnu: cedille: Adjust import list. > > This is a followup t

Re: haskell changes

Hi Robert, Timothy Sample writes: > Robert Vollmert writes: > >> I have some Haskell-related changes ready for review and ideally merge >> on wip-haskell-updates. > > Sounds good. I’ll take a look at that branch soon. > >> Changes are: >> 1. move li

Re: haskell changes

Hi Robert, Robert Vollmert writes: > Hi, > > I have some Haskell-related changes ready for review and ideally merge > on wip-haskell-updates. Sounds good. I’ll take a look at that branch soon. > I’ve tested them locally to the extent I managed; is CI broken or did I break > something there? h

Re: Please merge wip-haskell-updates (Re: [bug#36807] remove obsolete broken haskell packages)

Hi, Robert Vollmert writes: > On 8. Aug 2019, at 15:12, Marius Bakke wrote: >> I have one comment about the series: we've disabled tests on some >> packages that have been broken "forever" on i686. It would be better to >> do so selectively on just the affected architectures. I.e.: >> >> #:t

Re: Please merge wip-haskell-updates (Re: [bug#36807] remove obsolete broken haskell packages)

Hi Robert and Marius, Marius Bakke writes: > Robert Vollmert writes: > >> Oh, I meant to ask: >> >> On 6. Aug 2019, at 06:29, Timothy Sample wrote: >> >>> I think it makes sense to wait for the core-updates merge (which >>> shouldn’t be t

Re: Please merge wip-haskell-updates (Re: [bug#36807] remove obsolete broken haskell packages)

fit our conventions. I’ve added a few comments below. Robert Vollmert writes: > Hi Timothy, > >> On 6. Aug 2019, at 06:29, Timothy Sample wrote: >> >>> #36692: GHC version 8.6.5 (just as a package for now, not used to build >>>anything) >> >

Re: fixing GDM + GNOME Shell

Hello, Ricardo Wurmus writes: > Mark H Weaver writes: > >> It's interesting that I've never run into this problem, not even once, >> in all my years of running GNOME on Guix systems. Since recently >> reverting to mostly using GNOME under X and GDM (whereas for a while I >> was mostly launchin

Re: Please merge wip-haskell-updates (Re: [bug#36807] remove obsolete broken haskell packages)

Hi Robert, Robert Vollmert writes: > Hi all, Timothy, > > On 25. Jul 2019, at 15:29, Timothy Sample wrote: >> Other than that, LGTM. Thanks! (Do you have commit access now or >> should I push these?) > > I do have commit access now, but for the moment I’m keeping

Re: Non-bootstrappable NPM packages

Hi Jelle, Jelle Licht writes: > Timothy Sample writes: > > [snip] > >> I’ve come to think that bootstrapping JavaScript might be easier than it >> looks. As time goes on, Node gets better at the newer JavaScript >> features. This removes the need for thin

Non-bootstrappable NPM packages

Hi Guix, (I’m CC’ing swedebugia and Jelle on this, since I promised both of them off-list that I would publish this work eventually.) Most of us know that the JavaScript situation with Guix is a little dire. Particularly, some JavaScript packages have circular dependencies and most are not boots

Re: 01/01: gnu: evolution-data-server: Fix locale handling.

Hi Mark, Mark H Weaver writes: > Hi Timothy, > > guix-comm...@gnu.org writes: > >> samplet pushed a commit to branch core-updates >> in repository guix. >> >> commit d619686250d8bb15bf67031f8ac80f9cfb400a26 >> Author: Timothy Sample >> Date

Re: core-updates freeze

Hi Marius, Marius Bakke writes: > Timothy Sample writes: > >> From ad931895edae97e2d6d77542fcbe8dc793f193f0 Mon Sep 17 00:00:00 2001 >> From: Timothy Sample >> Date: Tue, 16 Jul 2019 10:04:58 -0400 >> Subject: [PATCH] system: Write the timezone to /etc/ti

Re: core-updates freeze

/35746#9> (here, “standard” means “well, I guess at least Gentoo does it”). Second, it is a one-liner for us: >From ad931895edae97e2d6d77542fcbe8dc793f193f0 Mon Sep 17 00:00:00 2001 From: Timothy Sample Date: Tue, 16 Jul 2019 10:04:58 -0400 Subject: [PATCH] system: Write the timezone to /e

Re: Fixing evolution-data-server on core-updates

Hello, Kei Kebreau writes: > Ludovic Courtès writes: > >> Hello Timothy, >> >> Timothy Sample skribis: >> >>> From bcd753f777687c52bba6b9bf4184879e69990118 Mon Sep 17 00:00:00 2001 >>> From: Timothy Sample >>> Date: Sun, 14 Jul 201

Fixing evolution-data-server on core-updates

rom: Timothy Sample Date: Sun, 14 Jul 2019 23:47:44 -0400 Subject: [PATCH] gnu: evolution-data-server: Fix locale issue. * gnu/packages/gnome.scm (evolution-data-server)[arguments]: Add a phase that patches the source code to fix a locale issue. --- gnu/packages/gnome.scm | 15 +++ 1 f

  1   2   >