Video license
Hello, while looking at the videos and the video-repository, I noticed that we don't have any license attached to neither the videos nor the sources. I think we should really add one. For the code I would suggest GPL v3+, for the voices (currently Paul) and videos I would suggest CC-BY-SA 4.0 [0]. What do you think? Does every contributor agree to that? Björn [0] https://creativecommons.org/licenses/by-sa/4.0/ pgpz9KAqbYAZ8.pgp Description: OpenPGP digital signature
Re: Documentation videos are being uploaded!
On Wed, 22 May 2019 14:06:17 -0300 Laura Lazzati wrote: > Hi Guix! > > I have created the site: https://archive.org/details/guix-videos > where I will be pushing the documentation videos that I created > during my internship and that Paul helped a a lot sharing their voice > and knowledge about video creation to enhance them. > > I appreciate feedback :) Hi, this is fantastic news! Thank you Laura for continuously caring about the videos even after your internship ended! Thank you Paul for giving your nice, calm English voice to the videos and in general your video-knowledge. Björn pgpz9LDwSQnxY.pgp Description: OpenPGP digital signature
Re: Running Guix System on Hetzner Cloud
Hi Jonathan,
Jonathan Brielmaier skribis:
> (initrd-modules '("virtio_scsi" "virtio_pci"))
The problem is like the ‘%base-packages’ bug: ‘%base-initrd-modules’ is
not added. :-/
Filed as . I’ll push a fix
shortly.
Thanks,
Ludo’.
Re: Let's merge staging!
Hello! Marius Bakke skribis: > The weather looks good (< 5% missing substitutes). I pushed a merge of > master just now to try and gain a better understanding of what is > missing before actually merging it. > > I suspect it's just the changes from 'master' since it was previously > merged to staging a while back, but Cuirass still is not as convenient > as Hydra for finding regressions, so better safe than sorry. > > I will merge it later today if things look OK. I think the merge hasn’t happened yet. :-) The stats I get for x86_64 after manually restarting the mariadb and gmime builds (the former needs more memory that build machines usually have, and the latter has a non-deterministic test failure it seems): --8<---cut here---start->8--- ludo@ribbon ~/src/guix$ ./staging/bin/guix describe Generacio 1 Jun 05 2019 12:57:12(nuna) guix 30e12b9 repository URL: https://git.savannah.gnu.org/git/guix.git branch: staging commit: 30e12b9664d774aca3948b1fa2e0aee6af09ca40 ludo@ribbon ~/src/guix$ ./staging/bin/guix weather -c10 -s x86_64-linux computing 9,851 package derivations for x86_64-linux... looking for 10,247 store items on https://ci.guix.gnu.org... https://ci.guix.gnu.org 78.8% substitutes available (8,072 out of 10,247) 25,062.2 MiB of nars (compressed) 69,325.7 MiB on disk (uncompressed) 0.000 seconds per request (4.4 seconds in total) 2,339.6 requests per second --8<---cut here---end--->8--- Thanks, Ludo’.
Re: Documentation videos are being uploaded!
Hi Laura, > Yes, sure! I also agree that it is important giving credits :) > Would you mind asking them if they want to have their name there? I have made a start and pushed a new CREDITS file to the repository. There are entries in the list for the contributors that I know about (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: wip-netlink
Hello,
Marius Bakke skribis:
> 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!
Yay!
> I *think* what I want is control over network interfaces. Something
> along the lines of
>
> (service network-interface-service-type
> "eth0"
> (network-interface-configuration
> (dhcp? #f)
> (ipv4 '("10.1.1.1/24" "172.16.30.4/22"))
> (ipv6 '(...))
> (routes4 '(("default" . "10.1.1.254")))
> (routes6 '(...))
> (requirement '(vswitchd
>
> Ideally, this service would extend "network-route-service-type" and
> "network-address-service-type" so that one could compose configurations
> from other services too. E.g. a custom VPN service that extends
> network-route-service-type.
Interesting! That sounds like a plan.
If there’s a separate “routes” service, perhaps the ‘routes4’ and
‘routes6’ fields could even be removed from
‘network-interface-configuration’?
We’d also need a ‘name-servers’ service I guess.
Also, in your example, ‘ipv4’ specifies both the IP and the netmask,
right? Perhaps we should separate the two?
Thanks,
Ludo’.
Re: Crosscompiling C++ for powerpc64le fails
Hi Marius, Marius Bakke skribis: > Ludovic Courtès writes: [...] >> The issue that Tobias reports reminds me of the CPATH vs. C_INCLUDE_PATH >> issue that was causing troubles with newer GCCs, and that I think Marius >> addressed in ‘core-updates’ (?). Marius, does that ring a bell? > > Unfortunately there are still issues with cross-compiling C++ on > 'core-updates'. For 'C', the workaround was to go back to "CROSS_CPATH" > instead of "CROSS_C_INCLUDE_PATH", like with native builds. That should also address C++, since CPATH (and CROSS_CPATH) are for all language front-ends, no just C, no? > For native builds on core-updates, GCC7 occasionally fails if the libc > or kernel headers are not on C_INCUDE_PATH (see e.g. f90d6c3). It could > be that cross builds need a similar workaround, but I have not found the > magic incantation yet. How can it be that kernel headers are not on C_INCLUDE_PATH (or CPATH)? On core-updates, I see that ‘gcc-6’ changes ‘native-search-paths’ from C_INCLUDE_PATH & co. to CPATH, and likewise, ‘cross-gcc’ sets ‘search-paths’ to CROSS_CPATH. That looks consistent to me. Ludo’.
Re: SELinux log
Hi Laura, > Today I've been installing Guix on top of Fedora (relase30), and I > faced issues with guix-daemon, getting it did not have permissions for > running. It was a SELinux problem, since after disabling it and > restarting the daemon I could use guix normally. > Here is my audit.log file […] Thanks. Did you install the SELinux policy for the daemon that is included in the source code repository? (It is not included in the files that “guix pull” installs.) -- Ricardo
