packaging: what to do about these requiring systemd?
Some packages require systemd; some may provide configure stage options to disable systemd support which can be supplied by the package definitions in Guix. But for these that do not make systemd support configurable, what is the general approach to make such packages available in GNU Guix?
Re: merging r-team branch
On Sun, Jul 07, 2024 at 09:24:23AM +0200, Ricardo Wurmus wrote: > Hi Guix, > > the r-team branch has been built successfully. It contains updates to R > and both CRAN and Bioconductor packages. > > It is the last in the queue of branches to be merged: > > core-updates #70456 > tex-team #70915 > python-team #71408 > kde-team #71614 > rust-team#71703 > r-team #71901 > > It touches very few packages that are not related to R. The exception > is apache-arrow. > > I know that while the python-team branch is farther up the queue it is > not actually ready to be merged, pushing up kde-team, rust-team, and > r-team. What is the status of the other branches in the queue? The rust-team has no objections to you merging first. -- Efraim Flashner רנשלפ םירפא GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
Re: Trying to update my Guix on Android
I copied those files from my debian system, will try with guix system later: adb push /etc/protocols /system/etc/ adb push /etc/services /system/etc/ adb push /etc/resolv.conf /system/etc/ And none of the files differ OnePlus6T:/etc # diff protocols /system/etc/protocols OnePlus6T:/etc # diff services /system/etc/services OnePlus6T:/etc # diff resolv.conf /system/etc/resolv.conf This one is working: /gnu/store/q7527zanapb5cqqsyj46m3q3yr8a3vvz-curl-8.5.0/bin/curl http://gnu.org 301 Moved Permanently Moved Permanently The document has moved http://www.gnu.org/;>here. Apache/2.4.29 Server at gnu.org Port 80 This one does not: OnePlus6T:/data/guixandroid # /gnu/store/q7527zanapb5cqqsyj46m3q3yr8a3vvz-curl-8.5.0/bin/curl https://gnu.org curl: (60) server certificate verification failed. CAfile: none CRLfile: none More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. Guix pull fails for the same reason /gnu/store/q7527zanapb5cqqsyj46m3q3yr8a3vvz-curl-8.5.0/bin/curl http://gnu.org zcat /var/log/guix/drvs/r6/39b2xgqihb2r1p8wqw25miid09s8mc-isrg-root- x2.pem.drv.gz View build log at '/var/log/guix/drvs/r6/39b2xgqihb2r1p8wqw25miid09s8mc-isrg-root- x2.pem.drv.gz'. cannot build derivation `/gnu/store/qlqq5kddrjmwsj8qfgcadklmmf7kx54j- le-certs-1.drv': 1 dependencies couldn't be built guix pull: error: build of `/gnu/store/qlqq5kddrjmwsj8qfgcadklmmf7kx54j-le-certs-1.drv' failed 1|OnePlus6T:/data/guixandroid # zcat /var/log/guix/drvs/r6/39b2xgqihb2r1p8wqw25miid09s8mc-isrg-root- x2.pem.drv.gz Starting download of /gnu/store/5ryjiaii7gn8imh2xix4mak2yk6gmgrl-isrg- root-x2.pem >From https://letsencrypt.org/certs/isrg-root-x2.pem... In procedure getaddrinfo: Temporary failure in name resolution
Re: merging r-team branch
Hello, Am Sun, Jul 07, 2024 at 09:24:23AM +0200 schrieb Ricardo Wurmus: > the r-team branch has been built successfully. It contains updates to R > and both CRAN and Bioconductor packages. > It touches very few packages that are not related to R. The exception > is apache-arrow. answering the subtext of the question, I think it would be okay to merge the branch before the others (or rather, independently). I see that there is a new patch on core-updates related to R: Author: Ludovic Courtès Date: Sun Jul 7 00:42:43 2024 +0200 gnu: r-minimal: Add dependency on ‘texlive-etoolbox’. * gnu/packages/statistics.scm (r-with-tests)[native-inputs]: Add TEXLIVE-ETOOLBOX. Change-Id: I1ea48e5afa013d8c36054f423e57252dbc02f12a So when merging first r-team and then core-updates or the other way round, it would be good to pay attention to it. Andreas
Re: merging r-team branch
Hello, Ricardo Wurmus writes: > the r-team branch has been built successfully. It contains updates to R > and both CRAN and Bioconductor packages. > > It is the last in the queue of branches to be merged: > > core-updates #70456 > tex-team #70915 > python-team #71408 > kde-team #71614 > rust-team#71703 > r-team #71901 > > It touches very few packages that are not related to R. The exception > is apache-arrow. > > I know that while the python-team branch is farther up the queue it is > not actually ready to be merged, pushing up kde-team, rust-team, and > r-team. What is the status of the other branches in the queue? The tex-team branch is included in core-updates and currently being built by the bordeaux farm. So it can be ignored. Regards, -- Nicolas Goaziou
Re: merging r-team branch
Ricardo Wurmus writes: > Hi Guix, > > the r-team branch has been built successfully. It contains updates to > R > and both CRAN and Bioconductor packages. > > It is the last in the queue of branches to be merged: > > core-updates #70456 > tex-team #70915 > python-team #71408 > kde-team #71614 > rust-team#71703 > r-team #71901 > > It touches very few packages that are not related to R. The exception > is apache-arrow. > > I know that while the python-team branch is farther up the queue it is > not actually ready to be merged, pushing up kde-team, rust-team, and > r-team. What is the status of the other branches in the queue? Kde-team wasn't ready yet and I opened question to get qa to show the broken package signature.asc Description: PGP signature
merging r-team branch
Hi Guix, the r-team branch has been built successfully. It contains updates to R and both CRAN and Bioconductor packages. It is the last in the queue of branches to be merged: core-updates #70456 tex-team #70915 python-team #71408 kde-team #71614 rust-team#71703 r-team #71901 It touches very few packages that are not related to R. The exception is apache-arrow. I know that while the python-team branch is farther up the queue it is not actually ready to be merged, pushing up kde-team, rust-team, and r-team. What is the status of the other branches in the queue? -- Ricardo
