Re: Some team related thoughts and questions...
On 2023-01-06, Simon Tournier wrote: > On Tue, 03 Jan 2023 at 22:11, Vagrant Cascadian wrote: > >> Perhaps a description would for the team(s) would help a bit here. I >> see embedded as dealing with bootloaders or firmware commonly used on >> embedded systems, and perhaps cross-compilers? > > Well, currently the ’team’ record contains the description field. So it > can be expanded if it helps. Right, there was no description for the "Embedded / Bootstrap" team ... so basically asking what the intention of the team is (and a little confused at the co-mingling of two seemingly distinct teams, at least in my mind). >> I wonder if the team.scm script could also have a few regexps in it for >> the patch description. For example, "deterministic" or "reproducible" >> might be a useful search term for my recently proposed Reproducible >> Builds team, which otherwise would only be interested in a small pool of >> reproducible builds tooling packages, but reproducible builds issues >> actually could be relevent for all packages in guix. > > I guess something like, > > ./etc/teams.scm list-teams | recsel -q deterministic > > should list the teams where ’deterministic’ appears. It is far from > being perfect but it allows minimal queries. More I wanted to look through the patch text rather than the package descriptions. It would ideally catch things like "reproducible" or "deterministic" in comments in patches as well as git commit summary. >> Lastly, I use the name "Vagrant Cascadian" with my contributions to >> guix, but I may use a different email address depending on the nature of >> the contribution (e.g. reproducible builds). I am not sure what would >> happen if I added "Vagrant Cascadian" twice, with two different email >> addresses. Does it handle that reasonably? > > You would like to have an email address different depending on the > team, right? > > Currently, a person (record ) has one name (string) and one > email (string) and then this person is part of one more teams (list). > > Well, it is not implemented but the macro ’define-member’ could be > tweaked to associate one email to one team for a person, I guess. If a "person" is identified by "name"+"email" then it should be fine. I was worried if a "person" is identified solely by "name". Defining myself as two persons with the same name and different email addresses works for my needs, if that is indeed how it works! live well, vagrant signature.asc Description: PGP signature
Re: Some team related thoughts and questions...
Hi Vagrant, On Tue, 03 Jan 2023 at 22:11, Vagrant Cascadian wrote: > Perhaps a description would for the team(s) would help a bit here. I > see embedded as dealing with bootloaders or firmware commonly used on > embedded systems, and perhaps cross-compilers? Well, currently the ’team’ record contains the description field. So it can be expanded if it helps. > I wonder if the team.scm script could also have a few regexps in it for > the patch description. For example, "deterministic" or "reproducible" > might be a useful search term for my recently proposed Reproducible > Builds team, which otherwise would only be interested in a small pool of > reproducible builds tooling packages, but reproducible builds issues > actually could be relevent for all packages in guix. I guess something like, ./etc/teams.scm list-teams | recsel -q deterministic should list the teams where ’deterministic’ appears. It is far from being perfect but it allows minimal queries. > Lastly, I use the name "Vagrant Cascadian" with my contributions to > guix, but I may use a different email address depending on the nature of > the contribution (e.g. reproducible builds). I am not sure what would > happen if I added "Vagrant Cascadian" twice, with two different email > addresses. Does it handle that reasonably? You would like to have an email address different depending on the team, right? Currently, a person (record ) has one name (string) and one email (string) and then this person is part of one more teams (list). Well, it is not implemented but the macro ’define-member’ could be tweaked to associate one email to one team for a person, I guess. Cheers, simon
Re: Suggest improve emacs setting in 'The Perfect Setup'
Hi, Thanks for sharing. Interesting to see other config. On Fri, 30 Dec 2022 at 08:54, Feng Shu wrote: > ;; ** Let geiser-guile use 'guix repl' > (setq geiser-guile-binary (list "guix" "repl" "-L" eh-geeguix-dir)) Be careful, this can bite you. :-) Guile is run with --no-auto-compile so the debugger is probably not working as expected. See [1,2]. 1: https://yhetil.org/guix/86o7ss1u49@gmail.com 2: https://yhetil.org/guix/87lenve3t2@gnu.org > ;; ** Get guix dir installed by 'guix pull'. > (defun eh-guix-dir () > (file-name-as-directory >(cl-find-if > (lambda (dir) > (file-exists-p (expand-file-name "guix.scm" dir))) > (directory-files > (expand-file-name "~/.cache/guix/checkouts/") > t Well, I do not know what you do with this but if you manually write in this directory, then “guix pull” could be then broken. Cheers, simon
Re: LaTeX packaging policy
Hi, On Sat, 24 Dec 2022 at 13:03, Josselin Poiret wrote: > While using a bit of LaTeX recently, I've noticed some packages don't > work "out-of-the-box", at least on LuaLaTeX, and need some additional > propagated inputs. Examples would be babel-french needing scalefnt, > fontspec needing luaotfload, or hyperref needing stringenc. Is there > any established policy for what propagated-inputs need to be included in > package definitions? Should we add some LaTeX specific packaging > guidelines in the manual, like for Python or Rust (the former is > outdated by the way, mentioning Python 2 packages). All the inputs are they required as propagated-inputs? Or only some? Maybe it could be worth to fix the broken packages (the examples above) and see if a pattern emerge for writing down a policy. Or maybe, we could propagate all the inputs since TeX can be considered as stable enough for minimizing the clash of versions. Cheers, simon
Be careful with PyPI
Hi, If the origin does not exist upstream, then Guix try other servers as fallback. For instance, --8<---cut here---start->8--- Starting download of /gnu/store/lb0kb4c212f9f789ixd1c18bcm8qbsqi-Keras-2.11.0.tar.gz >From >https://files.pythonhosted.org/packages/source/K/Keras/Keras-2.11.0.tar.gz... download failed "https://files.pythonhosted.org/packages/source/K/Keras/Keras-2.11.0.tar.gz; 404 "Not Found" Starting download of /gnu/store/lb0kb4c212f9f789ixd1c18bcm8qbsqi-Keras-2.11.0.tar.gz >From >https://ci.guix.gnu.org/file/Keras-2.11.0.tar.gz/sha256/1j8bsqzh49vjdxy6l1k4iwax5vpjzniynyd041xjavdzvfii1dlh... download failed "https://ci.guix.gnu.org/file/Keras-2.11.0.tar.gz/sha256/1j8bsqzh49vjdxy6l1k4iwax5vpjzniynyd041xjavdzvfii1dlh; 404 "Not Found" Starting download of /gnu/store/lb0kb4c212f9f789ixd1c18bcm8qbsqi-Keras-2.11.0.tar.gz >From >https://tarballs.nixos.org/sha256/1j8bsqzh49vjdxy6l1k4iwax5vpjzniynyd041xjavdzvfii1dlh... following redirection to `https://tarballs.nixos.org/sha512/0d57cb8e0af234a619ba3dec245c2ab73cbd0566194ed6b59377231183b2ef916514ba87abe04ec7e518770c9e0cb157747db87cedf0ebeced4ae0f56be401c3'... downloading from https://tarballs.nixos.org/sha256/1j8bsqzh49vjdxy6l1k4iwax5vpjzniynyd041xjavdzvfii1dlh ... 1j8bsqzh49vjdxy6l1k4iwax5vpjzniynyd041xjavdzvfii1dlh 748KiB 67.1MiB/s 00:00 [##] 100.0% successfully built /gnu/store/75g4aq5b25g4j1qwd3ggl1sys24q63la-Keras-2.11.0.tar.gz.drv --8<---cut here---end--->8--- One potential issue is that the tarballs.nixos.org is using the checksum as lookup key. Therefore, when modifying only the version and not the checksum, the something is returned with an inconsistent name/content. First, let get the source of the current Keras (v2.2.4). --8<---cut here---start->8--- $ ./pre-inst-env guix build python-keras -S 0.5 MB will be downloaded: /gnu/store/k2wxrqzmr29rjy1w5b0nhd4k36sv8szb-Keras-2.2.4.tar.xz substituting /gnu/store/k2wxrqzmr29rjy1w5b0nhd4k36sv8szb-Keras-2.2.4.tar.xz... downloading from https://ci.guix.gnu.org/nar/k2wxrqzmr29rjy1w5b0nhd4k36sv8szb-Keras-2.2.4.tar.xz ... Keras-2.2.4.tar.xz 521KiB 3.6MiB/s 00:00 [##] 100.0% /gnu/store/k2wxrqzmr29rjy1w5b0nhd4k36sv8szb-Keras-2.2.4.tar.xz --8<---cut here---end--->8--- Then, tweak only the version (update to 2.11.0) and get the source. --8<---cut here---start->8--- $ git diff diff --git a/gnu/packages/machine-learning.scm b/gnu/packages/machine-learning.scm index 75cc100851..2cbe0eddd6 100644 --- a/gnu/packages/machine-learning.scm +++ b/gnu/packages/machine-learning.scm @@ -2831,7 +2831,7 @@ (define-public python-keras-preprocessing (define-public python-keras (package (name "python-keras") -(version "2.2.4") +(version "2.11.0") (source (origin (method url-fetch) $ ./pre-inst-env guix build python-keras -S ;;; note: source file /home/simon/src/guix/guix/gnu/packages/machine-learning.scm ;;; newer than compiled /home/simon/src/guix/guix/gnu/packages/machine-learning.go ;;; note: source file /home/simon/src/guix/guix/gnu/packages/machine-learning.scm ;;; newer than compiled /home/simon/src/guix/guix/gnu/packages/machine-learning.go ;;; note: source file /home/simon/src/guix/guix/gnu/packages/machine-learning.scm ;;; newer than compiled /home/simon/.config/guix/profiles/emacs/emacs/lib/guile/3.0/site-ccache/gnu/packages/machine-learning.go ;;; note: source file /home/simon/src/guix/guix/gnu/packages/machine-learning.scm ;;; newer than compiled /home/simon/.config/guix/profiles/emacs/emacs/lib/guile/3.0/site-ccache/gnu/packages/machine-learning.go substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0% substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'... 100.0% The following derivations will be built: /gnu/store/by6pgdambmv4wrg2h40l287d7zhbwc17-Keras-2.11.0.tar.xz.drv /gnu/store/75g4aq5b25g4j1qwd3ggl1sys24q63la-Keras-2.11.0.tar.gz.drv building /gnu/store/75g4aq5b25g4j1qwd3ggl1sys24q63la-Keras-2.11.0.tar.gz.drv... Starting download of /gnu/store/lb0kb4c212f9f789ixd1c18bcm8qbsqi-Keras-2.11.0.tar.gz >From >https://files.pythonhosted.org/packages/source/K/Keras/Keras-2.11.0.tar.gz... download failed "https://files.pythonhosted.org/packages/source/K/Keras/Keras-2.11.0.tar.gz; 404 "Not Found" Starting download of /gnu/store/lb0kb4c212f9f789ixd1c18bcm8qbsqi-Keras-2.11.0.tar.gz >From >https://ci.guix.gnu.org/file/Keras-2.11.0.tar.gz/sha256/1j8bsqzh49vjdxy6l1k4iwax5vpjzniynyd041xjavdzvfii1dlh... download failed "https://ci.guix.gnu.org/file/Keras-2.11.0.tar.gz/sha256/1j8bsqzh49vjdxy6l1k4iwax5vpjzniynyd041xjavdzvfii1dlh; 404
