Marius,
guix-comm...@gnu.org wrote:
commit abb53e6f871cbf79fe24b7052fb41c8aff2f65ac
Author: Marius Bakke
Date: Mon Jun 3 18:32:56 2019 +0200
gnu: python-beautifulsoup4: Update to 4.7.1.
Thanks, as always! I've been gravely negligent in my update
duties of late.
+
Ludovic Courtès writes:
> If you’ve ever experienced the shortcomings of
> ‘static-networking-service’ and had to work around it, please share the
> interface that you’d like to see!
Hey, that's me!
I *think* what I want is control over network interfaces. Something
along the lines of
Am 03.06.19 um 18:19 schrieb Pronaip:
- All data comes with provenance tracking:
- computations are tracked via Guix
- human input is logged (interactivity) or version controlled
unless you vision of the distant future somehow also includes most social
problems having been
Pierre Neidhardt writes:
> Marius Bakke writes:
>
>> Can you share the patch? (guix utils) should not trigger a world
>> rebuild AFAIK.
>
> Yes, that's what I've been told, but I tried both (guix build utils) and
> (guix utils), they both resulted in a world rebuilt. Unless I did
> something
Ludovic Courtès writes:
> Hi Danny,
>
> Danny Milosavljevic skribis:
>
>> I've investigated a bit more:
>>
>> Guix's gcc-4.7 passes
>>
>> (string-append "--with-native-system-header-dir=" libc "/include")
>> where libc is (assoc-ref %build-inputs "libc")
>>
>> .
>>
>> However, further down,
Pierre Neidhardt writes:
> Is it too late to merge #36000 (guix: Add helper for generating desktop
> entry files.)?
Staging is currently 'frozen' pending a merge, so yes.
> It's non-disruptive but since it modifiers (guix utils) it triggers a
> world rebuild.
Can you share the patch? (guix
Mike Gran writes:
Hi!
>> I've just noticed test/closures.c -- is that intended for handlers like
>> key-press-event; are they different from `clicked'?
>
> This is me trying to explain to myself how the meta_marshaller was working
> in PyGObject, on which much of this code is based.
Ah, that
Hi, not to rain on the parade, but
> - All data lives in IPFS: no local filesystem, no Guix store.
> A personal computing device only stores references to information
> that its owner cares about.
>
> - All computations are equal: no distinction between "software builds"
> and
Ludovic Courtès writes:
> Hi!
>
> Marius Bakke skribis:
>
>> The staging branch has been accumulating updates for a while now.
>> We have Mesa 19, Sphinx 2.0, GStreamer 1.16, ALSA 1.1.9, as well as some
>> Python updates. See `git shortlog -n master..staging` for the scoop.
>>
>> I suggest we
Hi Pierre,
> I'm going to the IPFS camp (https://camp.ipfs.io/) on June 27th and I've
> been asked to give a (5 minute) lightning talk about IPFS & Guix. Yaik! :)
That sounds like a great opportunity. Guix and IPFS are in my humble
opinion two of the most interesting ongoing projects in the
On Mon, Jun 03, 2019 at 04:33:17PM +0200, Danny Milosavljevic wrote:
> Florian successfully tried kernel argument "blacklist=radeon" in the past--but
> I think that caused either VESA or EFI VGA to be picked and made the installer
> work.
>
Before modprobe.blacklist=radeon was added to the
Note: In current master, "radeon" is blacklisted. (See gnu/system/install.scm
kernel-arguments)
We might want to extend it to "radeon,amdgpu" if we still get reports of
problems with that.
pgpJzzBJV8P_I.pgp
Description: OpenPGP digital signature
There's also a vesa fb driver so X is still not necessary. (Our installation
media has already so much stuff on it, let's not increase it further)
For GPUs that are (sometimes) troublesome we should find out a way to
automatically blacklist the native modules so vesa gets picked.
Florian
13 matches
Mail list logo
