Re: Video narration

needed: N = s / i This method would be unaffected by disk write times or rounding errors. Best regards, Paul.

Re: Video narration

uld be. Can you confirm that you get the same result? Best regards, Paul.

Re: Video narration

eck the inner sleep commands in the way that you did before I can adjust the ending sleep to make sure that the 'apad' filter works correctly. How about that? Best regards, Paul.

Re: Video narration

- use1 again tomorrow. Best regards, Paul.

Re: Video narration

ct for these videos. I plan to finish the coarse level sleep settings for the remaining videos in the next few days. Best regards, Paul.

Re: Video narration

xample, it needs to be added back in elsewhere. Best regards, Paul.

Re: Video narration

rticular output is displayed slightly ahead of the narration one could add some extra sleep before the section and remove the same amount after. That way the total duration, of each session, will stay the same. Best regards, Paul.

Re: Video narration

18.04. Best regards, Paul.

Re: Video narration

test has revealed a bug in the Guix packaging of totem. Best regards, Paul.

Re: Documentation videos are being uploaded!

Hi All, > Kudos Laura & Paul! > I am cc'ing Paul :) It is good to hear that the end result is being well received :) I am thinking of adding a CREDITS file to the repository, primarily to acknowledge the help given by the sound engineer. The use of the studio equipment and t

Re: Packaging FreeCAD

All being well, I should be able to start on this within the next two weeks. I will update this thread when the package is ready. Best regards, Paul.

Re: Packaging FreeCAD

Hi John, > Another question: do we tend to try to use guix packages whenever a package > ships bundled with some third party source? Yes. The preference is to use Guix packages where possible. Best regards, Paul.

Re: Documentation videos are being uploaded!

thanks, Ricardo!) but I suspect that there has been more work done than I am aware of. Would you like to take a look and fill in the gaps? I have seen the names of Gabor and Bjorn in the logs, for example. Best regards, Paul.

Re: Video license

Hello Björn, > For the code I would suggest GPL v3+, for the voices (currently Paul) > and videos I would suggest CC-BY-SA 4.0 > > What do you think? Does every contributor agree to that? That looks good to me. For the source code we could add copyright statements at the top of

Re: Packaging FreeCAD

contains other CAD-related packages such as LibreCAD and KiCad. Best regards, Paul.

Re: (Really) Free Software future Was: Re: Proposal to remove the off-topic, ...

On Mon, 2019-10-14 at 12:07 +0200, Svante Signell wrote: > Perhaps we should divide free software into two groups: 1) Really > free software where Freedom 1 applies and 2) not-so-free software > where Freedom 1 does no longer applies. > > Here gnome and systemd are in the second kind. Both GNOME

Re: (Really) Free Software future

On Mon, 2019-10-14 at 18:52 +0200, Svante Signell wrote: > On Mon, 2019-10-14 at 12:13 -0400, Paul Smith wrote: > > On Mon, 2019-10-14 at 12:07 +0200, Svante Signell wrote: > > > Perhaps we should divide free software into two groups: 1) Really > > > free software wh

Re: (Really) Free Software future

On Mon, 2019-10-14 at 21:32 +0300, Alexander Vdolainen wrote: > > For example, no aspect of either GNOME or systemd are proprietary, > > using the common meaning of the term. Also, "lock-in" usually refers > > to software that prevents users from switching to an alternative; GNOME > > and systemd

Cross-building GuixSD (and maybe using pre-built toolchains)

nimal system and then natively building packages. Or have I misunderstood the process? Is it possible to cross-build all of the packages in the distribution? I hope I haven't missed anything that tells me the answers to all of these questions. Thanks in advance for any answers you may have! Pau

guix refresh error

ead-number #) In ice-9/boot-9.scm: 1685:16 1 (raise-exception _ #:continuable? _) 1683:16 0 (raise-exception _ #:continuable? _) ice-9/boot-9.scm:1683:16: In procedure raise-exception: Throw to key `json-invalid' with args `(#)'. Are others seeing this too? Best regards, Paul.

Re: Committers: create and share your Codeberg account

Hi Guix, Ludovic Courtès writes: > To avoid problems, I suggest you send your account name as a public > reply to this message, in a signed message. I am pgarlick; https://codeberg.org/pgarlick Best regards, Paul. signature.asc Description: This is a digitally signed message part

git-fetch without a hash

Hello Guix! It seem that url-fetch will work without a hash (that is, with (sha256 #f)) but git-fetch will not. As near as I can tell this is because git-fetch uses a fixed derivation build going via nix/build.cc stuff which contains this line: if (i.second.hash == "") fixedOutput =

Re: git-fetch without a hash

However, there's no real reason that git-fetch *needs* to be fixed-output in terms of having a hash pre-defined, at least for local development and other purposes. So is there a way around this? • write (package (source (git-checkout …)) …) This works well. Now I'm curious how to know what

Re: git-fetch without a hash

Once we update the ‘guix’ package, the daemon will no longer accept ‘url-fetch’ downloads with hash = #f. Ok. Is there something like (git-checkout) we can use that will work instead of an (origin) here for url downloads?

Re: Racket packages / build system

Thanks for the notes. I've skimmed through them and they seem sensible. I'll look at how other build systems are written as a first step, then get my hands wet. Do I open an issue for this I've recently become interested in this as well. I pinged cwebber asking for the best place to start and

A hacky prototype for using ipfs to provide binary substitutes to users

Hi! After some discussions on #guix on irc.freenode.org with ludovic, p9kill, roptat, swedebugia, and others which I sadly forgot, I decided to scramble together a proof-of-concept hacky prototype for a mechanism to share binary substitutes via ipfs. There are two parts to this: 1] A hacky guix p

Re: A hacky prototype for using ipfs to provide binary substitutes to users

Nice! I tried to take a look at the existing ipfs-wip branches and felt it was too difficult for me to package myself. Good luck with it! Flo Am 30/11/2018 um 09:56 schrieb Pierre Neidhardt: Fantastic news! I'll be most interested by this, especially since I've been working on packaging IPFS

Re: guix is the guildhall that we always wanted!

On 03/16/2017 11:24 PM, Ludovic Courtès wrote: I think having repos maintained elsewhere is OKish, but it’s true that it requires people who maintain those repos to follow closely what’s going on in Guix proper because we’re not guaranteeing API stability. Wouldn't taking the functional/reprodu

Test failures on new build

Trying to get an environment for hacking on Guix going on my new computer. Installed guix on my Debian stable using guix-install.sh then ran guix pull. Did a fresh git clone on guix then guix environment guix --pure ./bootstrap ./configure --localstatedir=/var make -j24 make -j24 check mostly wo

Re: Test failures on new build

Could you attach tests/guix-git-authenticate.log? Likewise. Likewise. Likewise. Attached. + '[' -d /home/singpolyma/src/guix/.git ']' + guile -c '(use-modules (git)) (member "refs/heads/keyring" (branch-list (repository-open ".")))' + intro_commit=9edb3f66fd807b096b48283debdcddccfea34bad + in

Adding Trilinos to dealii package

channel for dealii configured with Trilinos (the inferiorer option :)). - Some other possibility I have not thought of. Thank you and best regards, Paul [1]: https://github.com/lethe-cfd/lethe [2]: https://www.dealii.org/current/external-libs/petsc.html [3]: https://www.dealii.org/cur

What is the standard path for documentation?

d files as documentation, but I thought I saw the source of a Guix package make an attempt to strip build directory information from one of its output files. Thanks, Paul ### # # deal.II configuration: #CMAKE_BUILD_TYPE: DebugRelease #BUILD_SHARED_LIBS: ON #CMAKE_INST

Re: What is the standard path for documentation?

; Thus, I would not install these two files, especially since they seem to > be redundant with Guix-supported provenance tracking. Thanks, that's what I decided to do (i.e., delete the files). Best regards, Paul

Getting GEM_PATH right for ruby scripts

Hello everyone! I've finally been diving deep into the Guix and doing a lot of packaging. One thing that has now come to my attention is the way ruby-build-system set GEM_PATH for wrapped scripts. It takes the whole GEM_PATH that is present at build time. This means that all those packages end

Re: WIP: neomutt. segfaulting outside of gdb, functional inside.

On 27.06.2016 09:58, Ricardo Wurmus wrote: ng0 writes: In gnu/packages/mail.scm I created this package. It builds succesfully, but when I run it, it segfaults. Running it in gdb however makes it succeed and not segfault. How do I debug such a software? Have you tried running with “strace -f

Separate Mailing Lists for Patches vs General Dev Discussion?

Hi, I'm following the Guix-Project, even if not contributing much because of time constraints. The one, very simple to implement, thing that would make following the project more easy IMHO would be a separate list for patches. Or maybe the other way around: A separate list for more general di

Re: [GSoC] Continuous integration tool à la Hydra.

On 07/25/2016 11:36 PM, Ludovic Courtès wrote: >> For those willing to follow my work, a Git repository is available here: >> >> https://notabug.org/mthl/cuirass > > … and the README has instructions on how to run it. If anyone has spare > CPU cycles, run Cuirass, ‘guix publish’, and share. :

Re: [GSoC] Continuous integration tool à la Hydra.

Hi! On 07/29/2016 09:26 PM, Mathieu Lirzin wrote: >> To get pkg-config, see . >> See `config.log' for more details > > I have tested successfully with the following command on a foreign > system: > > guix environment --ad-hoc automake pkg-config guile guix l

Re: [GSoC] Continuous integration tool à la Hydra.

Hi again. Sorry I'm on vacation in Sweden so the formatting of this mail suffered ;) The one thing that had me worried was the errors right after the git pull.. Regards, Flo On July 31, 2016 2:03:59 PM GMT+02:00, Mathieu Lirzin wrote: >Hi, > >Florian Paul Schmidt writes: >

Re: [PATCH] Fix compiling on CentOS 7.

On 08/27/2016 10:51 AM, Roel Janssen wrote: > I don't see a way to apply this patch "on the CentOS side" except for > waiting (another two or three years) until they upgrade Automake. When packaging guix for CentOS, just add a patch to the source package definition.. Regards, Flo P.S.: Why the

proposal: (define (find-guix-packages list-of-names) ... )

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I found a procedure like this (then at the top of my system config.scm's) to be quite useful: diff --git a/gnu/packages.scm b/gnu/packages.scm index fb27738..63500ab 100644 - --- a/gnu/packages.scm +++ b/gnu/packages.scm @@ -228,6 +228,14 @@ de

Re: proposal: (define (find-guix-packages list-of-names) ... )

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, and thanks for your reply.. On 11/15/2015 09:35 PM, Ludovic Courtès wrote: > I think ‘specification->package’ from (gnu packages) is the > procedure you want. Like this: > > (map specification->package '("guile-2" "gnupg-2.0" "coreutils")) >

Re: proposal: (define (find-guix-packages list-of-names) ... )

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/16/2015 02:03 PM, Ludovic Courtès wrote: > Florian Paul Schmidt skribis: > > I’m fine with documenting ‘specification->package’ as an alternate > option. Its semantics are exactly the same as when referring to a > pack

Re: proposal: (define (find-guix-packages list-of-names) ... )

On Mon, 16 Nov 2015 21:06:00 +0100 l...@gnu.org (Ludovic Courtès) wrote: > Sure. I think we would need a new section for (gnu packages), maybe > “Distribution API” under “GNU Distribution”? It would describe > ‘fold-packages’, ‘specification->package’, and so on. Let's start smaller :) [I'm sti

[PATCH, WIP] new variable: redshift

How could anyone live without this? I am disappoint.. I couldn't try it on bare metal yet and the drm and randr methods fail in qemu. Maybe someone can test it? Thanks? Flo diff --git a/gnu/packages/xdisorg.scm b/gnu/packages/xdisorg.scm index 4b5308c..c0ef4bc 100644 --- a/gnu/packages/xdisorg.sc

Re: [PATCH, WIP] new variable: redshift

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/24/2015 09:28 AM, Florian Paul Schmidt wrote: > How could anyone live without this? I am disappoint.. I couldn't > try it on bare metal yet and the drm and randr methods fail in > qemu. Maybe someone can test it? Thanks? >

Re: [PATCH, WIP] new variable: redshift

Updated diff --git a/gnu/packages/xdisorg.scm b/gnu/packages/xdisorg.scm index 4b5308c..2b07ea5 100644 --- a/gnu/packages/xdisorg.scm +++ b/gnu/packages/xdisorg.scm @@ -655,3 +655,28 @@ use it as well.") "The xf86-input-wacom driver is the wacom-specific X11 input driver for the X.Org X Ser

Re: [PATCH, WIP] new variable: redshift

Updated to make lint happy diff --git a/gnu/packages/xdisorg.scm b/gnu/packages/xdisorg.scm index 4b5308c..6a84e8c 100644 --- a/gnu/packages/xdisorg.scm +++ b/gnu/packages/xdisorg.scm @@ -655,3 +655,33 @@ use it as well.") "The xf86-input-wacom driver is the wacom-specific X11 input driver f

proposal: make build failures explicit results in the store

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, currently I'm trying my hands on building _all_ available packages on the x86_64 platform in a qemu-vm (with the intended aim to later publish them to maybe take some load off hydra), but I came across an issue that might have an easy solution

Re: proposal: make build failures explicit results in the store

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/25/2015 09:14 AM, Florian Paul Schmidt wrote: > Afaict the real problem is that the functional approach is slightly > broken here (being functional is fine, just the implementation is > broken). The attempt to build bar _had_ a res

Re: [PATCH, WIP] new variable: redshift

On 11/24/2015 04:59 PM, Jeff Mickey wrote: > Don't know what others think, but we should probably also package > redshift-gtk if we're gonna include redshift. Mine has a bug where > icons don't show up so I didn't push it, but see here for what I > use locally: > > https://github.com/codemac/

Re: proposal: make build failures explicit results in the store

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/25/2015 02:22 PM, Ludovic Courtès wrote: > taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis: > >> You can run the Guix daemon with the switch --cache-failures and >> it will do pretty much exactly what you want. :-) > > Yep.

Re: proposal: make build failures explicit results in the store

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/25/2015 03:19 PM, Florian Paul Schmidt wrote: > Oh, I wasn't even aware there was a DB. I had a more functional > picture in mind where there was a map > I guess I should have written "simpler" instead of

Re: [PATCH, WIP] new variable: redshift

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/25/2015 01:47 PM, Ludovic Courtès wrote: > I see your redshift package is also slightly more elaborate. Would > you like to submit it (or Florian can incorporate the differences)? > Here are some comments: > >> +(synopsis + "Adjusts

Re: proposal: make build failures explicit results in the store

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/25/2015 10:49 PM, Ludovic Courtès wrote: > Florian Paul Schmidt skribis: > >> Oh, I wasn't even aware there was a DB. I had a more functional >> picture in mind where there was a map > > See > <http

Re: [PATCH] openssh: install ssh-copy-id.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/27/2015 11:38 AM, Ricardo Wurmus wrote: > This fixes bug #22024. > Wow, thanks :) Flo - -- https://fps.io -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJWWIXZAAoJEA5f4Coltk8ZlksH/18HM9V/ao40QXgVw06D0lO2 8xeVcGXmCJV5Nv4S7ju

Re: proposal: (define (find-guix-packages list-of-names) ... )

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/28/2015 04:39 PM, Ludovic Courtès wrote: >> Let's start smaller :) > > I rearranged the text and ended up with something different from > your original patch but hopefully as informative in f6c9fb1. And more concise :) Thanks, Flo - -- h

proposal: add "packagers" field (list of strings (names)) to package definition

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 ...and encourage its use. The intended semantics is to list people that have contributed to the packaging effort. The motivation behind this proposal is that in many free software projects attribution can be a major source of motivation to get peopl

Re: proposal: add "packagers" field (list of strings (names)) to package definition

On 12/01/2015 09:12 AM, Florian Paul Schmidt wrote: > > ...and encourage its use. The intended semantics is to list people > that have contributed to the packaging effort. The motivation > behind [...] Something like: diff --git a/guix/packages.scm b/guix/packages.scm index 68fb

Re: proposal: add "packagers" field (list of strings (names)) to package definition

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/02/2015 03:09 PM, Thompson, David wrote: >> The kind of ego-based positive feedback that having a maintainer >> field would introduce is negative IMO. It is good if people feel >> attached to Guix-the-project and >> GuixSD-the-software-distri

Re: proposal: add "packagers" field (list of strings (names)) to package definition

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/02/2015 05:50 PM, Andreas Enge wrote: > The problem with attributions is that it is also exclusive of > others who might contribute to the package otherwise. It can create > tendencies to "own" packages, which creates a barrier for others to >

Re: proposal: add "packagers" field (list of strings (names)) to package definition

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/02/2015 05:12 PM, Andy Wingo wrote: > If there are other ways we can recognize people's work, we should > consider them :) Think of it this way though, a packager is a > person who packages. The value is in the verb, not the noun; > packagi

Re: proposal: add "packagers" field (list of strings (names)) to package definition

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/01/2015 06:35 PM, Leo Famulari wrote: > All the contributors do get attribution in the copyright notice at > the top of each file, although that information is not linked to > their actual contributions except through git. If they feel their

[PATCH]: xfce4-power-manager: new variable

the minimal set for which ones the package build still succeeds? ;) [lazy flo] From 5ca12ed7fd62792b856aa686e66dfc224e16bf35 Mon Sep 17 00:00:00 2001 From: Florian Paul Schmidt Date: Thu, 3 Dec 2015 14:57:10 +0100 Subject: [PATCH] xfce4-power-manager: new variable --- gnu/packages/xfce.scm

Re: proposal: add "packagers" field (list of strings (names)) to package definition

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/03/2015 05:46 PM, Pjotr Prins wrote: > On Wed, Dec 02, 2015 at 03:59:52PM +0100, Florian Paul Schmidt > wrote: >> Aww, too bad. I think it's a missed opportunity to be inclusive >> and generous with attribution which m

Re: proposal: add "packagers" field (list of strings (names)) to package definition

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/03/2015 11:36 AM, Ludovic Courtès wrote: > Florian, do you have other ideas on how we could publicly show our > appreciation of contributions? Not right now. If any ever occurs to me I'll let you guys know ;) Flo - -- https://fps.io

Re: [PATCH]: xfce4-power-manager: new variable

Removed some inputs (see attached patch). Seems to still build and run.. Flo On 12/03/2015 03:04 PM, Florian Paul Schmidt wrote: Hi, attached is a patch for a first stab at packaging xfce4-power-manager. Since I used a different package as a base for this one there might be some unneeded

Re: [PATCH]: xfce4-power-manager: new variable

Make lint happy On 12/03/2015 10:40 PM, Florian Paul Schmidt wrote: Removed some inputs (see attached patch). Seems to still build and run.. Flo From be4925c1fb459ef02965a771dc0689f5dc23b2e3 Mon Sep 17 00:00:00 2001 From: Florian Paul Schmidt Date: Thu, 3 Dec 2015 22:43:06 +0100 Subject

Re: [PATCH]: xfce4-power-manager: new variable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/04/2015 06:16 PM, Andreas Enge wrote: > On Thu, Dec 03, 2015 at 10:40:50PM +0100, Florian Paul Schmidt > wrote: >> Removed some inputs (see attached patch). Seems to still build >> and run.. > > I usually work the

Re: [PATCH]: xfce4-power-manager: new variable

Remove some more crud. On 12/03/2015 10:43 PM, Florian Paul Schmidt wrote: Make lint happy On 12/03/2015 10:40 PM, Florian Paul Schmidt wrote: Removed some inputs (see attached patch). Seems to still build and run.. Flo From 6d4ce3ad7a0298bdf8b445e9384c00727800ded3 Mon Sep 17 00:00:00

Re: gnunet-gtk

On 12/06/2015 02:05 PM, anonymiss wrote: I wonder if somebody is working on gnunet-gtk or if this is a package I could get involved with in GuixSD packaging? Hi, I don't know whether anyone's working on that package, but I'd like to see it, just to play a little more with gnunet.. So I f

Re: [PATCH]: xfce4-power-manager: new variable

On 12/06/2015 10:51 PM, Ludovic Courtès wrote: Could you send the full patch in one go? Also please include a ChangeLog-style commit entry, and make sure ‘guix lint’ is happy before posting. :-) See . Thanks for help

swh-plugins-lv2: New variable [WIP]

Just pushing this out to get some feedback (I'll need to package more audio plugins and this might be a good start to talk about possible issues) See the attached diff.. Flo From 905622fe8bf6522765002a2ee3f7815b5bf458ea Mon Sep 17 00:00:00 2001 From: Florian Paul Schmidt Date: Wed,

Re: swh-plugins-lv2: New variable [WIP] v2

On 12/06/2015 11:44 PM, Florian Paul Schmidt wrote: Just pushing this out to get some feedback (I'll need to package more audio plugins and this might be a good start to talk about possible issues) Updated complete patch with some whitespace and typos fixed Flo

Re: swh-plugins-lv2: New variable [WIP] v2

On 12/07/2015 10:17 PM, Ricardo Wurmus wrote: Hi Florian, thanks for the patch! Hi rekado, thanks for the feedback :) The commit message should be: gnu: Add swh-plugins-lv2. * gnu/packages/audio.scm (swh-plugins-lv2): New variable. Oh drats, no more -a -m "lalalala" commits.

Re: [PATCH, WIP, v2] new variable: redshift

On 11/24/2015 09:28 AM, Florian Paul Schmidt wrote: > How could anyone live without this? I am disappoint.. I couldn't try it > on bare metal yet and the drm and randr methods fail in qemu. Maybe > someone can test it? Thanks? Version 2 of the patch. lint is happy. Some reco

Re: swh-plugins-lv2: New variable [WIP, v2]

On 12/06/2015 11:44 PM, Florian Paul Schmidt wrote: > Just pushing this out to get some feedback (I'll need to package more > audio plugins and this might be a good start to talk about possible issues) Updated the patch, since it seems the other version didn't get submitted..

Re: [PATCH] emacs: Use socket instead of port.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12.12.2015 09:50, Alex Kost wrote: > Currently, if you try to run a repl command (for example, "M-x > guix-installed-packages") in a second Emacs instance, you'll get > an unfriendly error. That's because `guix-default-port' is busy > already (b

substitutes mirror of 0.9.0 packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, this service might go away anytime. But I setup a substitute server that is reachable at http://fps.io: The public key is: (public-key (ecc (curve Ed25519) (q #AFF68C4E099401E85BE2D7375C1DB5E8A29F1DB83299038122AF5C0984099CF8#) )

Re: substitutes mirror of 0.9.0 packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 18.12.2015 10:25, Florian Paul Schmidt wrote: > It should have most of 0.9.0 packages and some random ones from > other revisions. I should qualify this statement by mentioning that it's x86_64 only.. Flo - -- https://fps.io ---

Re: substitutes mirror of 0.9.0 packages

On 12/18/2015 10:25 AM, Florian Paul Schmidt wrote: http://fps.io: The public key is: (public-key (ecc (curve Ed25519) (q #AFF68C4E099401E85BE2D7375C1DB5E8A29F1DB83299038122AF5C0984099CF8#) ) ) In case you wondered about how to use this (which I just only found out myself

Re: substitutes mirror of 0.9.0 packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 20.12.2015 21:31, Leo Famulari wrote: >> guix package -i boost --substitute-urls="http://fps.io:"; > > The guix-daemon takes the argument "--substitute-urls", so you can > also use it system-wide without extra typing. And I guess to be on t

Re: Create help-g...@gnu.org?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 21.12.2015 14:45, Ludovic Courtès wrote: > Hello! > > Should we create a help-g...@gnu.org mailing list specifically to > answer user questions? Consistent naming schemes are important. I object. How about guix-h...@gnu.org :) Flo - -- htt

Re: Create help-g...@gnu.org?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 21.12.2015 17:21, Eric Bavier wrote: >>> Should we create a help-g...@gnu.org mailing list specifically >>> to answer user questions? >> >> Consistent naming schemes are important. I object. How about >> >> guix-h...@gnu.org > > I would agree w

Re: dmd’s new name

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07.01.2016 22:02, Ludovic Courtès wrote: > I proposed to Richard Stallman that we change the name to “GNU > Shepherd” and recently got the green light. It's corny, it's cheesy. I like it ;) Flo - -- https://fps.io -BEGIN PGP SIGNATURE---

Re: [PATCH] Refer to GuixSD as beta software

On 05.04.2016 14:08, Jelle Licht wrote: > Although it is mostly me nitpicking, I was installing GuixSD on an old > laptop and noticed that the message of the day of the installation image > still referred to GuixSD as alpha software. > > This patch changes the motd of the installer use the term be

autoconf-archive package [free form]

FYI: (define-public autoconf-archive (package (name "autoconf-archive") (version "2016.03.20") (source (origin (method url-fetch) (uri (string-append "http://mirror.bibleonline.ru/gnu/"; "autoconf-archive/autoconf-archive

Calling autogen.sh in a build

Hi, I'm trying to package rapicorn. And it's mostly gnu-build-system based, but I need to call autogen.sh (see below for package definitions). Sadly I suck and it fails. Got any ideas? Seems i need to rerun the patch-shebangs phase? Flo phase `patch-source-shebangs' succeeded after 0.1 seconds

Re: Calling autogen.sh in a build

Care to share? I'm eager to play around with Bease/BSE, that's why I pressed forward with it. Regards, Flo On 12.04.2016 09:42, Ricardo Wurmus wrote: Florian Paul Schmidt writes: I'm trying to package rapicorn. And it's mostly gnu-build-system based, but I need to

Re: [PATCH] Add rapicorn.

Hi, awesome! Do you also press ahead with packaging Beast? Just asking to avoid duplication of effort.. Flo On 13.04.2016 21:34, Ricardo Wurmus wrote: Hi Guix, this patch adds Rapicorn, the graphics library used by Beast. A new version of Rapicorn has just been released that removed a bund

Re: [PATCH] gnu: Add Red Eclipse.

On 23.04.2016 08:20, Kei Yamashita wrote: > With much help from others on IRC, this patch works! If necessary > or preferable, please suggest changes to make this patch more > maintainable in the long run. > Hi, I think you forgot to attach the patch :) Flo -- https://fps.io signature.asc

Xorg video inside VirtualBox

Hello all, I hope i won't commit any grave errors of etiquette, since this is my first post here. I've been experimenting with installing Guix inside a VirtualBox virtual machine, and it's pretty cool. I'm even managing to figure out how to install packages ;) My problem is thus: i've inst

Re: [PATCH] bump mu/mu4e to version 0.9.11

Hi Mark, > Looks good to me, modulo a few minor nits. Thanks for the feedback! I've tried again, see attachment. Cheers, p. >From 579637f64f075c25028479a259ae860fe276efa6 Mon Sep 17 00:00:00 2001 From: Paul van der Walt Date: Fri, 27 Feb 2015 01:23:48 +0100 Subject: [PATCH] gnu: mu

[PATCH] Update ncmpcpp to v0.6.2

Hello again, A patch to update ncmpcpp, the mpd frontend. I hope my patch makes more sense now -- the build system is a little finicky, so perhaps there's a neater way to accomplish what i'm doing. Thanks, p. >From e1382a9df3e7df94e794df8aa247920b7e28c0c6 Mon Sep 17 00:00:00 2001 F

Re: [PATCH] Update ncmpcpp to v0.6.2

Hi, I'm a little busy for now, but i'll get to this soon. Thanks for your comments! On 2015-02-27 at 17:13, quoth Mark H Weaver: >> Paul van der Walt writes: > [...] >>> +(arguments >>> + '(#:configure-flags >>> + '("BOO

Re: [PATCH] Update ncmpcpp to v0.6.2

On 2015-02-27 at 19:21, quoth Mark H Weaver: > On the whole, I think the preferable approach (and the one I've used in > a large commit that cleans up all of these autogen-style phases) is > this: > > --8<---cut here---start->8--- >(alist-cons-after >

[PATCH] ncmpcpp version update, mail.scm copyright line

the name of the GNU multiprecision library. What should i call this mpc package? Since i know that Guixers are prone to long debates about names (i jest :p), here's my single suggestion: * mpc-client Bye! p. >From 0963038a01ff1b3c1646d58a2eae0f92180cb8f7 Mon Sep 17 00:00:00 2001 From:

Re: [PATCH] ncmpcpp version update, mail.scm copyright line

On 2015-02-28 at 16:04, quoth David Thompson: > I've pushed these patches. I modified your commit log to say "0.6.2" > instead of "v0.6.2", changed past tense verbs to present tense, and left > out the part about copyright. Thanks! >> * mpc-client > > Perhaps the GNU MPC package should be calle

[PATCH] Add mpc, the mpd client

Hello, Here's mpc, packaged as mpd-mpc, since mpc, Andreas' library, has already squatted the name 'mpc' :p Unhello, p. >From 20110c1b5d4761b26910d8958d150ced68c1c60a Mon Sep 17 00:00:00 2001 From: Paul van der Walt Date: Sat, 28 Feb 2015 18:22:03 +0100 Subject: [PATCH

[Sebastian Ramacher] Re: zathura license

Hello Guix, I'd like to package a program with the "zlib license" which i hadn't heard of before. How would i do that given that it seems `license:..` terms only exist for GPL and BSD, roughly? According to The Internet this license is GPL compatible, so can i go ahead? Thanks, p. On 2015-02-28

<    1   2   3   4   5   6   >