Re: Clarifying blog post licensing
I agree. pelzflorian (Florian Pelz) ezt írta (időpont: 2022. jan. 27., Cs 18:35): > I agree. > > On Wed, Jan 26, 2022 at 10:24:11AM +0100, Ludovic Courtès wrote: > > Hello Guix! > > > > With a few exceptions, our blog posts do not have a license, which is > > not great as it prevents sharing and reuse, at least by those outside > > Guix circles (we discussed it in the past but never got around to fixing > > it). > > > > I’d like us to clarify that, with a footer on blog posts saying that, > > unless otherwise stated, posts are dual-licensed under CC-BY-SA 4.0 and > > GFDL 1.3+ (the latter so we can reuse material in the cookbook and in > > the manual). Patch below. > > > > What do people think? > > > > If maintainers and everyone agrees, I’d like to publicly email all the > > authors asking them whether they agree with the proposed licensing > > terms, or whether they’d like a different free license. The script > > below enumerates blog post authors (the list needs a bit of cleanup > > still): > >
gwl-0.4.0 released [stable]
We are pleased to announce the release of the GNU Guix Workflow Language version 0.4.0, representing 60 commits by one person that are the result of discussions among a number of helpful people on the #guix and #guix-hpc IRC channels on libera.chat and on the gwl-de...@gnu.org mailing list. Special thanks go to Simon Tournier and Ludovic Courtès for their patience, support, and insightful comments. The biggest change compared to the previous release is likely the support of job submissions to an HPC job scheduler via DRMAA, using the new Guile bindings for DRMAA v1[1]. These Guile bindings would not have been possible without Matt Wette, his helpful comments, and his most excellent FFI helper (part of nyacc). [1]: https://git.elephly.net/software/guile-drmaa.git [2]: https://www.nongnu.org/nyacc/ For details see the NEWS excerpt below. See also the updated manual: https://workflows.guix.info/manual/ An real-world example workflow is included in the doc/examples/pigx-rnaseq directory of the source repository. • About The Guix Workflow Language (GWL) provides an extension to GNU Guix's declarative language for package management to automate the execution of programs in scientific workflows. The GWL can use process engines to integrate with various computing environments. • Download Here are the compressed sources and a GPG detached signature[*]: https://ftpmirror.gnu.org/gwl/gwl-0.4.0.tar.gz https://ftpmirror.gnu.org/gwl/gwl-0.4.0.tar.gz.sig Use a mirror for higher download bandwidth: https://www.gnu.org/order/ftp.html [*] Use a .sig file to verify that the corresponding file (without the .sig suffix) is intact. First, be sure to download both the .sig file and the corresponding tarball. Then, run a command like this: gpg --verify gwl-0.4.0.tar.gz.sig If that command fails because you don't have the required public key, then run this command to import it: gpg --keyserver keys.openpgp.org --recv-keys BCA689B636553801C3C62150197A5888235FACAC and rerun the 'gpg --verify' command. This release was bootstrapped with the following tools: Autoconf 2.69 Automake 1.16.3 Gnulib v0.1-3269-g03d7a6b1f NEWS * Changes in 0.4.0 (since 0.3.0) ** Workflow syntax - the new =workflow= fields =before= and =after= can be used to specify procedures that are run before and after the workflow runs. This can be useful for printing banners or further instructions. - new procedure =display-file= to print the content of files ** Execution engines - Process engines can now specify a procedure in the =check= field to validate the execution environment before running the workflow. - Process engines have a new =run= field specifying how ordered processes should be iterated over. - The new =drmaa-engine= supports job submission to schedulers implementing DRMAA version 1. - The =grid-engine= is deprecated and will be removed in future releases. Use the =drmaa-engine= instead. ** Bug fixes - the cache feature would symlink if hardlinking was not possible. This was incorrect and now it falls back to copying files to and from the cache when hardlinking fails. -- Ricardo signature.asc Description: PGP signature
Re: disable suspend without user login
On 2022-01-28, Attila Lendvai wrote: >> The first reply already says what you have to do, i.e. set those two > > my problem was that i didn't know how to run dbus-launch on Guix. > > the proper incantation on Guix is: > > $ guix install glib:bin xhost > $ xhost + > $ ll `which gsettings` > $ su - > # su --login gdm --shell `which bash` > -bash-5.1$ dbus-launch > /gnu/store/567jgb5q1cr7xmqsd5kairrdj66ihhy9-glib-2.70.0-bin/bin/gsettings set > org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing' Be very careful with "xhost +", from the xhost manpage: + Access is granted to everyone, even if they aren't on the list (i.e., access control is turned off). X is also a network-transparent protocol, so read-write access to your display from any user on your system or potentially on the network opens the door wide for keyloggers or other ways to steal passphrases, data on disk, etc. live well, vagrant signature.asc Description: PGP signature
Re: Return back original implementation for text-config serialization
On 2022-01-27 00:04, Maxim Cournoyer wrote: > Hi Andrew, > > Andrew Tropin writes: > > [...] > >> Ludovic mentioned someday that nginx-configuration is problematic, but I >> highlighted the generic problems, which are applicable for many other >> guix service configurations. >> >> I discussed some other pros and cons of record-based configurations in >> https://issues.guix.gnu.org/52698 >> >> and I see the benifits of the records, but I'm not sure if they >> outweight the weaknesses. >> >> It maybe sound unrelated to this thread, but it's actually very ontopic, >> because it lead to the design and implementation of home services >> configuration approach in general and slurp-file-gexp and text-config in >> particular. > > Pardon my ignorance about Guix Home, but couldn't we have configuration > as records by default, and the lower level, config stitching primitives > still available to hand craft strings that could be used as the value of > an 'extra-config' field, for example? extra-config/extra-content/file doesn't play well with the rest of configuration record. See the proposed patch, which introduces home service for redshift: https://issues.guix.gnu.org/53466 I briefly mentioned it, but can elaborate if necessary. To be clear the top-level SOMETHING-configuration still being the record, fields, which introduces some complex changes like shepherd-service? or something-else-quite-big still fields of this record, but what get serialized to config file will be mostly a plain datastructure in the approach I propose and recommend. > It seems to me the use of records for configurations in Guix Home would > be the natural choice, as Guix System users are already familiar with > them and it leans to better discoverability/documentation. The point about Guix System users is valid, however I don't see it as a big paradigm shift or very different approach. I made a few points about discoverability/documentation in issue about redshift. -- Best regards, Andrew Tropin signature.asc Description: PGP signature
Re: The way to promote GUIX package manager
On +2022-01-27 22:43:06 -0300, David Pirotte wrote: > > > ... > > What does "apt search guix" produce? > > (Nothing, on the puri.sm variant of debian. They maintain a custom > > pool based on debian minus what they want to exclude AIUI) > > fwiw, > > > https://packages.debian.org/search?keywords=guix=names=all=all Yeah, forgot to mention: they don't _prevent_ you from doing anything you want -- in fact that's what they're about: to ensure that you (having the necesssary expertise or funds to hire it) _can_ control as near as possible everything your computer does, including (not quite all) IME firmware, bios, bootloaders and the whole chain onwards. OTOH they may not want to spend a lot of time helping you undo what you did to yourself by bypassing their packages and safeguards. They may instead suggest you install QubesOS and run iffy stuff (like guix, whose reproducibility unfortunately does not exclude reproducing bugs and vulnerabilities :) in a dom for untrusted sfw. Personally, I like simplicity best, so I am watching MES and RISC-V and hoping for a "stateless" laptop which will bootload _anything_ into memory from _anywhere_ -- and ask me (via trustable interface) if I like the sha256 it computed for the image just loaded. Bonus for asking me if I want it to check or add to white-list via secure protocol to USB goodie. With only hot-pluggable high speed disks, I can just with keep my precious stuff fully separate and unconnected while I take internet advice like "just run everything as root, it makes it so much easier for a newbie." ;-) I think SeaBIOS and a doctored kernel-independent grub can get close, but I want stateless with _all_ hot-pluggable hard disks, even if two (for raid or cloning) of them have convenience slots to hold them as cartridges. Dreaming on ... -- Regards, Bengt Richter
Re: disable suspend without user login
> The first reply already says what you have to do, i.e. set those two my problem was that i didn't know how to run dbus-launch on Guix. the proper incantation on Guix is: $ guix install glib:bin xhost $ xhost + $ ll `which gsettings` $ su - # su --login gdm --shell `which bash` -bash-5.1$ dbus-launch /gnu/store/567jgb5q1cr7xmqsd5kairrdj66ihhy9-glib-2.70.0-bin/bin/gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing' is this worthy for the cookbook, shall i send it in a patch? the other method, namely to produce a patched gdm package, is still beyond my expertise at this point. -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- “The supreme art of war is to subdue the enemy without fighting.” — Sun Tzu (c. 6th century BC), 'The Art of War'
