[PATCH 2/2] gnu: ddcui: Update to 0.3.0.
* gnu/packages/hardware.scm (ddcui): Update to 0.3.0. [arguments]: Use new style. --- gnu/packages/hardware.scm | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gnu/packages/hardware.scm b/gnu/packages/hardware.scm index 18261d381d..7603bcb71e 100644 --- a/gnu/packages/hardware.scm +++ b/gnu/packages/hardware.scm @@ -520,7 +520,7 @@ (define-public ddcutil (define-public ddcui (package (name "ddcui") -(version "0.2.1") +(version "0.3.0") (source (origin (method git-fetch) @@ -529,10 +529,10 @@ (define-public ddcui (commit (string-append "v" version (file-name (git-file-name name version)) (sha256 -(base32 "0a9xfv80dpimx9wi9igjbbfydyfsgnbk6dv1plhjzyp2a9shdibb" +(base32 "0gypfmwxhjmgyfwk29k8hfbgr0698kbcq2yj4izxv1i59zm63irz" (build-system cmake-build-system) (arguments - '(#:tests? #f)); No test suite + (list #:tests? #f)); No test suite (native-inputs (list pkg-config qttools-5)) (inputs -- 2.37.3
[PATCH 1/2] gnu: ddcutil: Update to 1.3.2.
* gnu/packages/hardware.scm (ddcutil): Update to 1.3.2. --- gnu/packages/hardware.scm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gnu/packages/hardware.scm b/gnu/packages/hardware.scm index d47be7a55d..18261d381d 100644 --- a/gnu/packages/hardware.scm +++ b/gnu/packages/hardware.scm @@ -476,14 +476,14 @@ (define-public ckb-next (define-public ddcutil (package (name "ddcutil") -(version "1.2.2") +(version "1.3.2") (source (origin (method url-fetch) (uri (string-append "https://www.ddcutil.com/tarballs/"; "ddcutil-" version ".tar.gz")) (sha256 -(base32 "18fbd45h2r3r702dvmlmyrwgs3ymr4mhm4f12lgv9jqb5csalbw2" +(base32 "0hm0cm4m4hk1jjy7kddg613mynvwlii3kp8al0j9v3c6mcx3p4mx" (build-system gnu-build-system) (native-inputs (list pkg-config)) base-commit: 68f09d1f91793a6ff6412d9cc88daca148a0b30d -- 2.37.3
Re: Why linux-libre-bpf?
Hi my fellow Guix, On Sat, Oct 8, 2022 at 5:32 PM wrote: > > > CONFIG_BPF_JIT_ALWAYS_ON=y > > CONFIG_BPF_JIT=y > > > > Why is this not the default in regular linux-libre? Maybe it's historical. I believe JIT used to open a side-channel for the Spectre attack. [1] Kind regards Felix Lechner [1] https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html
Re: Why linux-libre-bpf?
October 8, 2022 8:18 PM, "kiasoc5" wrote: > AFAIK Guix is the only distro with a separate kernel (linux-libre-bpf) > that has the following turned on: > > CONFIG_BPF_JIT_ALWAYS_ON=y > CONFIG_BPF_JIT=y > > Why is this not the default in regular linux-libre? > I just did a quick internet search for the ebpf vulnerabilities. A few came up. Maybe it's a security feature. :) > --
Re: Packaging docs
I don't know what other commiters think about that, but you could try and suggest a concrete change. Can you write a patch, or at least a paragraph and point to the location it should go to, in the manual? Le 8 octobre 2022 19:24:31 GMT+02:00, jgart a écrit : >On Sat, 08 Oct 2022 08:08:28 +0200 Julien Lepiller wrote: >> I don't think there's a specific policy, but our packages tend to enable >> most optional dependencies and docs are always useful, so I'd package doc >> dependencies too. >> > >Hi roptat, > >Should we make a policy and add it to the docs? > >-- >jgart > >
Re: Packaging docs
On Sat, 08 Oct 2022 08:08:28 +0200 Julien Lepiller wrote: > I don't think there's a specific policy, but our packages tend to enable most > optional dependencies and docs are always useful, so I'd package doc > dependencies too. > Hi roptat, Should we make a policy and add it to the docs? -- jgart
Re: Advanced network configuration
Hi Julien, I sent patches to guile-netlink [1]. Footnotes: [1] https://issues.guix.gnu.org/58382 -- Alexey
Small change request to the manual page "Building from Git"
Hi there, I'd like to request some small changes be made on this page: > https://guix.gnu.org/manual/en/html_node/Building-from-Git.html 1. Authenticating on a foreign distro When at the "make authenticate" stage of the build process on a foreign distro, this fails because it cannot find guix. I think it's because the `guix environment guix --pure' command doesn't include it, or obscures its path. As a workaround, I ran `PATH=/usr/local/bin/:$PATH make authenticate' Seems simple enough, but might cause some trouble for inexperienced users such as myself who might not know whether or not the environment command was an optional step. 2. Easy fix for failing `make check' tests I had a few failing tests on my foreign distro relating to setting locales. Digging around led me to this reddit thread for the solution: > https://old.reddit.com/r/GUIX/comments/jpq1uw/bashminimal507binbash_warning_setlocale_lc_all/ Here they suggest running `sudo guix install glibc-locales` instead of as a user. Maybe this should be mentioned, since I'm not the only one coming to GUIX from another distro. Thanks otherwise for the fantastic manual, Best, M
Re: Could the Go importer use the Go toolchain? (was Re: Go importer and packages with version flags)
Hello, After a hiatus I am trying to package several softwares written on Golang (I would like to have terraform and go-jsonnet for example) and I have some problems with the current implementation so I am resurrecting this old mail from my Draft folder. Looking at it I think it is mostly reformulations of what Katherine and Sarah already wrote on the thread but several months later it could be a useful reminder. I have not really the energy at the moment to work on this alone but I would be interested for team work. On Thu, Sep 30, 2021 at 10:31:08AM -0500, Katherine Cox-Buday wrote: > Sarah Morgensen writes: > > >> IMO, module resolution and graph dependencies in Go are complicated enough > >> that I'd much rather take the effort we put in trying to replicate and keep > >> up with the Go toolchain's behavior, and spend that effort elsewhere. > >> > >> Does anyone have opinions on this? > > > > Hmmm. Setting aside whether or not we want to use external tools in > > general... > > > > If we use the Go tool, we shift the problem domain into "translating between > > `go' and Guix." I felt uneasy when we reimplemented some inherently Go-specific pieces of software like go.mod file parsing and dependency resolution. It seems so brittle. So I think that for importer specifically we should be able to use external programs like the Go toolchain to be in $PATH. And, given the Go tool would have proper interfaces, we would indeed just have to do some sort of translation. But as to the exact "how" it is not easy. Ideally we could split the tasks in severals steps. 1. identify all dependencies on form of go modules paths 2. identify source repositories (generally identified by a git-ref) for each of those modules 3. download content of source repository 4. populate a ready-to-use source code local cache 5. build As I see it in Guix we want : - 1 and 2 in the importer; - 3 is the "origin" method; - 4 and 5 in the build system. `go mod download` does all of 1, 2 and 3. The translations problems are how to extract data from this output to isolate dependency management on the importer and having the necessary info for the "origin" method. Nix bypass completely the problem by using the complete go mod cache as its "origin" (or more recently "vendored" dependencies see this Nix change to go mod vendor[4]) for each Go package. This solution is not viable for us as we want to be able to reuse Go modules. For the build system part I think we want to use the GOMODCACHE format as output of Guix package and to be able to do union-dir of all dependencies when we want to build a leaf package (e.g. using GOPROXY=file:/// or something like that). > > For example: when Go downloads a module, it only saves the module, not the > > whole repository*, so we can't use that to generate the hash. (* Except it > > does if you used GOPROXY=direct, but that's in the module cache, and only a > > bare repository.) > > We could use the ~GOMODCACHE~ environment variable[0] to specify where these > files are placed. Yes we want to do that but it leaves open as to how we create this directory structure. I think it is good to use Go tooling at "guix import" time but not at build time. In consequence the source must be downloaded either from upstream git repo (bare or not I do not know) or as zips from proxy.golang.org. The zip solution could just parse the directory contents of GOMODCACHE as described in [5]. I would rather import git repositories closer to real source but it seems more difficult to do. Even with zip, it leaves open the problem of mapping source zips with Guix packages and to handle the dependencies correctly. Any interest on the matter ? François [4]: https://github.com/NixOS/nixpkgs/pull/86376/commits/9761128d2da7bf4d878982918242e43ae28f9b94 [5]: https://github.com/golang/go/issues/35922#issuecomment-560464243 cd go/src/golang.org/x/tools/gopls # or any other module export GOPATH=$(mktemp -d) go mod download find $GOPATH/pkg/mod/cache/download -type f | \ grep '\.\(mod\|info\|zip\)$' | \ sed -e "s,$GOPATH/pkg/mod/cache/download,https://proxy.golang.org,";
