Re: 04/08: gnu: QEMU: Unbundle iPXE.

Mathieu Othacehe skriver: > Hello Marius, > >> glib >> gtk+ >> + ipxe-qemu >> libaio >> libcacard;smartcard support >> attr libcap-ng ;VirtFS support > > I just noticed that: > > --8<--

Re: 06/06: gnu: samba/fixed: Update to 4.15.13.

Hi Liliana, guix-comm...@gnu.org skriver: > lilyp pushed a commit to branch master > in repository guix. > > commit c39db91e51e55e46f177378c7b5a797441dc7d1b > Author: Liliana Marie Prikler > AuthorDate: Sun Dec 18 08:29:07 2022 +0100 > > gnu: samba/fixed: Update to 4.15.13. > > * gn

Re: 01/03: gnu: lld-as-ld-wrapper: Add version 15.

Christopher Baines skriver: > guix-comm...@gnu.org writes: > >> mbakke pushed a commit to branch master >> in repository guix. >> >> commit 65976a8382678cd983ceddde040b777cba1f1be9 >> Author: Marius Bakke >> AuthorDate: Thu Nov 17 07:22:41 2022 +

Re: Packages depending on (guix build syscalls)

Ludovic Courtès skriver: > Hi! > > Marius Bakke skribis: > >> Ludovic Courtès skriver: >> >>> Ludovic Courtès skribis: >>> >>>> Quite a few packages depend on (guix build syscalls), starting from >>>> ‘ant-bootstrap’ (since c

Re: Packages depending on (guix build syscalls)

Ludovic Courtès skriver: > Ludovic Courtès skribis: > >> Quite a few packages depend on (guix build syscalls), starting from >> ‘ant-bootstrap’ (since commit cded3a759356ff66b7df668bcdbdfa0daf96f4c5 >> in 2018) up to GNOME-related packages such as ‘mutter’ (commit >> d1c2fe248a7a326189fb7dcae64a

State of the 'core-updates' branch

Hello Guix, There has been a lot of activity on 'core-updates' recently. Some highlights from this branch: * The Full-Source Bootstrap * GCC 11 * glibc 2.35 * Python 3.10.7 * OpenSSL 3.0 * Meson 0.63.2 * CMake 3.24.2 * Pytest 7.1.3 * bash-completion 2.11 As well as updates to the usual low-leve

'staging' freeze

n 'master' I'm fairly rusty when it comes to Cuirass, and don't see a button to start the jobset here even when authenticated: https://ci.guix.gnu.org/jobset/staging Can someone remind me how to enable a disable jobset? :-) Full shortlog below: Marius Bakke (100):

Re: Who owns guix-mirror?

Tobias Geerinckx-Rice skriver: > Hi Philip, > > Philip Beadling 写道： >> I was wondering who owns the mirror as there is no public >> ownership declared on github.com? >> >> Is it owned by Guix or is it run by a trusted third party, etc? > > It

Re: branch master updated: gnu: python-lxml: Update to 4.6.5.

Danny Milosavljevic skriver: > Hi Mathieu, > > On Mon, 15 Aug 2022 16:24:03 +0200 > Mathieu Othacehe wrote: > >> > * gnu/packages/xml.scm (python-lxml): Update to 4.6.5. >> >> I had to revert it as it caused >15k rebuilds. I also cancelled all the >> triggered builds in the CI. > > Thanks

100k commits!

Guix, We just passed 100 000 commits! The lucky winner is ... commit 9fe9856ebef515927900e56686a1071936bdafcc Author: Ricardo Wurmus Date: Wed Aug 10 12:19:55 2022 +0200 gnu: r-fontawesome: Update to 0.3.0. * gnu/packages/cran.scm (r-fontawesome): Update to 0.3.0. An appr

Re: Dealing with non-ASCII file names in BOOTSTRAP-ORIGIN

Greg Hogan skriver: > On the off chance that the following is helpful, in order to switch > the build to GCC 11 or 12 I had to apply the patch (with the missing > endif) from > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017#c12 > > You may have avoided or worked around this issue, but even

Dealing with non-ASCII file names in BOOTSTRAP-ORIGIN

Hi Guix, I tried switching to GCC 11 on the core-updates branch, but it fails early when attempting to repack the GCC source code for GCC-BOOT0, because some files in its test suite contains non-ASCII characters: --8<---cut here---start->8--- [... unpacking ...

Re: Non-free data in Poppler test suite

Mark H Weaver skriver: > Therefore, I think that in order to comply with the FSDG, we should use > a snippet to remove any files covered by the CC BY-NC-ND license. The test suite is shipped separately from the Poppler source code, and contains many seemingly unauditable PDF files. I don't thin

Non-free data in Poppler test suite

Hello Guix, I discovered a potential freedom issue with the Poppler test suite. Specifically it includes a file with the CC BY-NC-ND (non-commercial) license: https://gitlab.freedesktop.org/poppler/test/-/commit/920c89f8f43bdfe8966c8e397e7f67f5302e9435 It turns out the repository is filled wi

Re: License of your contributions to the blog at guix.gnu.org

Ludovic Courtès skriver: > Hello, > > I am emailing you on behalf of the GNU Guix project because you are the > author or coauthor of one or more articles to the blog at > . > > With a few exceptions, these articles do not have a clear license, which > we would like

Re: Expat 2.3.0 has been released

Sebastian Pipping skriver: > Hello everyone, > > > just a quick heads up that there will be a new release of libexpat with > security fix in a few weeks. Unless I looked in the wrong place, I > noticed that your distro has not updated to libexpat 2.3.0 as of today. > If you ran into any issues

Re: A "cosmetic changes" commit that removes security fixes

Léo, We maintainers have been disappointed by Marks harsh tone which do not meet the project's communication standards, but also by your apparent lack of will to reply constructively to legitimate criticism. This is the next in a series of incidents. The incidents are okay--we we all make mistak

Re: [ungrafting] cURL is missing the 'curl-use-ssl-cert-env' patch

Marius Bakke skriver: > Now the question is: should we restore this patch, and in practice > restart the branch almost from scratch? Or drop it, considering > upstream has rejected it[0]? Following a discussion on IRC, we decided to reinstate the patch and get rid of the newly added

Polkit now depends on Rust

Hello, Newer versions of 'polkit' depend on mozjs 78, which unsurprisingly depends on Rust. As Rust currently only builds on x86_64, that means an important piece of desktop systems will no longer work on other architectures. How should we deal with this? I see a couple of options: 1. Stick wi

[ungrafting] cURL is missing the 'curl-use-ssl-cert-env' patch

Hello, As you may have noticed, there is a new "ungrafting" branch that intends to remove most of the "grafts" people have to deal with on a regular basis. The CI (and undersigned) have gotten pretty far on building this branch, but there is a problem: cURL lost its "curl-use-ssl-cert-env" patch

Re: Poetry upgrade and related packages

Tanguy LE CARROUR skriver: > Hi Marius, > > > Excerpts from Marius Bakke's message of December 7, 2020 11:59 pm: >> Tanguy LE CARROUR skriver: >>> Excerpts from Ludovic Courtès's message of December 5, 2020 4:44 pm: Tanguy LE CARROUR skribis: > It's not yet clear to me how to han

Re: updating Jami to "Together", Qt update?

Jan Wielkiewicz skriver: > Hello everyone, > > I managed to compile the latest release of Jami and I'll be sending > patches soon. > Is anyone planning to update Qt to 5.15.1? It would be nice if Jami > used this version to stay close to upstream. > I can update it if no one plans that. I have a

Re: Poetry upgrade and related packages

Tanguy LE CARROUR skriver: > Hi, > > > Excerpts from Ludovic Courtès's message of December 5, 2020 4:44 pm: >> Tanguy LE CARROUR skribis: >> >>> It's not yet clear to me how to handle (python) package updates: >>> - when to update; >>> - when not to update; >>> - when to introduce "versionned"

Re: 01/07: gnu: python-packaging: Update to 20.4.

Hello, guix-comm...@gnu.org skriver: > ngz pushed a commit to branch master > in repository guix. > > commit 71b15b4874b7f9ec7001d2916a8ab27dcce6cdc0 > Author: Tanguy Le Carrour > AuthorDate: Mon Nov 30 10:48:57 2020 +0100 > > gnu: python-packaging: Update to 20.4. > > * gnu/package

Re: GNU Guix 1.2.0rc1 available for testing!

"pelzflorian (Florian Pelz)" writes: > On Fri, Nov 13, 2020 at 06:07:32PM +0100, Ludovic Courtès wrote: >> system installation: >> […] >> >> https://alpha.gnu.org/gnu/guix/guix-system-install-1.2.0rc1.x86_64-linux.iso.xz > > Sorry for testing so late. For me the graphical installer cr

Re: branch master updated: gnu: nyxt: Update to 2-pre-release-3.

Pierre Neidhardt writes: >> I had not realized sbcl-static-dispatch failed to build even on 'master' >> initially, did you commit it by mistake? If I'd known I would not have >> let it hold up the merge. > > Weird, it works for me on be0ebf33aa19dcfd36c7a8d22a53344dc3b4a533 It did not work for

Re: branch master updated: gnu: nyxt: Update to 2-pre-release-3.

Pierre Neidhardt writes: > Marius Bakke writes: > >> Speaking of the Common Lisp build system on 'staging', the newly-added >> 'sbcl-static-dispatch' fails to build when merged or cherry-picked. >> >> Can you look into it? > > I haven&

Re: branch master updated: gnu: nyxt: Update to 2-pre-release-3.

Marius Bakke writes: > Pierre Neidhardt writes: > >> Can't wait for staging to merge, the Common Lisp build-system is vastly >> improved! > > I've just fixed a 'totem' test failure. Unless other regressions show > up it should be ready for merge w

Re: branch master updated: gnu: nyxt: Update to 2-pre-release-3.

Pierre Neidhardt writes: > I've just pushed a fix in 98a15c796afcc91894b7400b1d548cd50604db0c, so > Nyxt should be back to its pristine defintion. Oh my, thanks for catching that. I did have the lparallel removal in my notes and distinctly remember adjusting for it, but obviously messed up at s

Re: branch master updated: gnu: nyxt: Update to 2-pre-release-3.

Pierre Neidhardt writes: > Hi Marius! > > Sorry about this! :( > >> If you happen to be around right now, can you confirm that there were no >> changes to nyxt inputs in 573489fbcd68e3a89cc5c9c66693d3689b1b88bf? > > I don't have a Guix checkout at hand now so I can only tell you tomorrow. > Did y

Re: branch master updated: gnu: nyxt: Update to 2-pre-release-3.

Marius Bakke writes: > This is a friendly reminder to please list all changes to inputs, > arguments etc in the commit message. It makes resolving merge conflicts > *much* easier. > > Due to SBCL changes on the 'staging' branch, there have been a few > changes to th

Re: branch master updated: gnu: nyxt: Update to 2-pre-release-3.

Hello Pierre, guix-comm...@gnu.org writes: > commit 21e79225352a5e78aa329b6cd213eb553862c363 > Author: Pierre Neidhardt > AuthorDate: Tue Oct 20 15:06:59 2020 +0200 > > gnu: nyxt: Update to 2-pre-release-3. > > * gnu/packages/web-browsers.scm (nyxt): Update to 2-pre-release-3. > ---

Re: Update on the timeline for the release v1.2.

Julien Lepiller writes: > Le 21 octobre 2020 11:57:48 GMT-04:00, "Ludovic Courtès" a > écrit : >>zimoun skribis: >> > The proposed coming timeline is: > > - freeze starting the Oct. 26th > - last round for testing all over the week > - unfreeze the Oct. 29th and the

Re: Did nmap just become non-free?

Brett Gilio writes: > Marius Bakke writes: >> >> ...I'm fairly certain this is not an acceptable license for Guix, or >> free software distributions in general. >> > > This is definitely not a consistent license for us. Having re-read the original text (wi

Did nmap just become non-free?

Hello, I updated the nmap license in 2323a7120a0f3ed96fedfff42e86c0aee97995c0. Admittedly I had only skimmed through the text, which is "based on GPL2" and "believed to be compliant with the 'Open Source Definition'", but after a closer read of the annotated version: https://nmap.org/npsl/npsl-

Re: staging freeze

Julien Lepiller writes: > Le 13 octobre 2020 17:54:16 GMT-04:00, Marius Bakke a écrit : >>Hello Guix, >> >>I've pushed a set of updates to the long-overdue "staging" branch. >> >>Let's get it merged once Cuirass is done building for the vario

staging freeze

Hello Guix, I've pushed a set of updates to the long-overdue "staging" branch. Let's get it merged once Cuirass is done building for the various architectures. Not sure how long that takes now that we no longer use transparent QEMU emulation for AArch64 and armhf. signature.asc Description: PG

Re: etc/news copyright (was Re: Translating the web site)

Julien Lepiller writes: > OK for me too! Ditto for me (I think I mainly copy-pasted another news item anyway). signature.asc Description: PGP signature

Running service migrations during upgrades

Hello Guix, Some services require administrator interaction when they are updated. The most prominent examples here are MySQL/MariaDB and PostgresQL. For the former, running 'mysql_upgrade' in-place is generally sufficient and fairly safe. For the latter, the procedure is more involved, and requ

Re: [PATCH 0/X] gnu: poetry: Fix broken dependency after dependency's version update.

Tanguy Le Carrour writes: > Hi Guix! > > Few days ago, I submitted a patch to update `python-tomlkit`. It was pushed > to master and, after I upgraded my packages today, I realised that `poetry` > (and possibly other python packages) was broken! > > The "problem" is that Poetry depends on `tomlki

Re: guile-readline bug -- readline module not available

Josh Marshall writes: > Hello all, > > I ran into an issue where the readline module isn't available for the > guile repl after installing `guile-readline`. It can be replicated > via: > > `echo "(use-modules (ice-9 readline))" | guix environment --pure guile > guile-readline -- guile` > > So wi

Re: [Guix Website] A Search Page for Packages

Ludovic Courtès writes: > On berlin we’ll have to keep using nginx I guess (there’s too much > config in there), but perhaps Varnish is an option for the Data Service. To be clear, Varnish is not a replacement for nginx (it does not even speak HTTPS), the typical deployment is nginx -> Varnish -

Re: [Guix Website] A Search Page for Packages

Christopher Baines writes: > Ludovic Courtès writes: > >> Heya Danjela, >> >> Daniela Lura skribis: >> >>> Taking into consideration the suggestion made in this thread: >>> https://lists.gnu.org/archive/html/guix-devel/2020-05/msg00096.html, my >>> mentor, Christopher Baines suggested me to wri

Re: How to package inputrc

Efraim Flashner writes: > On Mon, Jul 13, 2020 at 09:30:31PM +0300, Efraim Flashner wrote: >> On Mon, Jul 13, 2020 at 11:26:59AM -0600, Jesse Gibbons wrote: >> > > In order to achieve this more elegant I could write a simple service to >> > > copy the file to /etc. Another option would be a small

Re: Pushed a fix (?) for ACL key location

Jonathan Brielmaier writes: > On 12.07.20 03:44, Christopher Lemmer Webber wrote: >> Commit 6680880f9b8dceb4f2f3f91bd2b13c659b53835e pushed out a new version >> of Guix, and it looks like it wasn't possible to build new systems from >> that because the filename for the "Berlin ACL key" changed.

Re: Pushed a fix (?) for ACL key location

Christopher Lemmer Webber writes: > Commit 6680880f9b8dceb4f2f3f91bd2b13c659b53835e pushed out a new version > of Guix, and it looks like it wasn't possible to build new systems from > that because the filename for the "Berlin ACL key" changed. (Or at > least, I couldn't run "guix system vm".) >

Re: hint: Run `guix search ... | less' to view all the results

Robin Templeton writes: > Seconded! The current behavior seems exactly backwards compared to most > *nix tools; if I wanted *less* information from "guix search" I'd > manually pipe the output into head or recsel. Perhaps Git-style > auto-pagination (i.e. page the results when outputting to a ter

Re: Reducing Mesa closure size

Pierre Neidhardt writes: > So what the following strategy: > > - Extract the various mesa drivers to separate package, > e.g. mesa-radeon, mesa-radeonsi, mesa-nouveau, etc. I think outputs are better suited for this. > - Modify xorg-wrapper to accept an extra `drivers' > parameter. > > - Ex

Re: branch staging updated: gnu: ghc-7: Clean up package definition.

Jakub Kądziołka writes: > On Tue, Jun 02, 2020 at 09:22:31PM +0200, Marius Bakke wrote: >> We should have a better way to poll branch status other than "read all >> messages on guix-devel" or "ask Marius on IRC". > > Ouch, sorry for that! I see two pote

Re: Downloader for "wrapped" tarbar?

Hartmut Goebel writes: > Hi, > > was just written in another mail, I'm currently working on a > erlang/rebar build system. This includes an importer from hex.pm, a > package repository for elixir and erlang packages. (Since this is build > into rebar3 I assume it what PyPI is for Python and CPAN

Re: branch staging updated: gnu: ghc-7: Clean up package definition.

guix-comm...@gnu.org writes: > This is an automated email from the git hooks/post-receive script. > > niedzejkob pushed a commit to branch staging > in repository guix. > > The following commit(s) were added to refs/heads/staging by this push: > new f20d1cf gnu: ghc-7: Clean up package defin

Re: Git repos with large submodules

raingloom writes: > Hey all! > > So, I recently gave a go to packaging EDK2 on my channel, and found out > that it requires several submodules, including OpenSSL, which take up > quite a bit of space and take way longer to download than necessary. > > Since I couldn't find a way to shallow-init t

Re: [PATCH] gnu: Add font-sarasa-gothic

Zhu Zihao writes: > You miss the right angle bracket in the copyright line > > It should be > > ;;; Copyright © 2020 Zhu Zihao Good catch, fixed in a8c7d4b0c326905b71680783ced6b68d25fb3bfd, thanks! signature.asc Description: PGP signature

Re: [PATCH] gnu: Add font-sarasa-gothic

Zhu Zihao writes: > This patch adds Sarasa Gothic. Sarasa Gothic is based on Iosevka and Source > Han > Sans, intends to make a really monospaced(inclduing CJK characters) > programming > fonts. In Sarasa Gothic, a normal CJK character is same height and double > width > as an ASCII character.

Re: Heads-up: hard reset of the 'staging' branch

Ludovic Courtès writes: > Hi! > > Marius Bakke skribis: > >> I have good news and bad news. The good news is that the new commit >> verification infrastructure works great. 'make authenticate' will >> verify that all commits were signed by a key that w

Re: Heads-up: hard reset of the 'staging' branch

Marius Bakke writes: > Marius Bakke writes: > >> I have pushed a 'staging2' branch where I did the following: >> >> 1) git rebase -i --rebase-merges 8229ce3116c1f522c7157ab2dcd50dc2d765686a~ >> >> 2) Moved

Re: Can we increase the print width/column in daemon backtraces

Pierre Neidhardt writes: > Marius Bakke writes: > >> You can run it directly from a shell, and/or attach a debugger. > > Thanks for the tip. > > Any idea how to attach Geiser to it? The daemon is a C++ program, so I'm not sure that would work ... If you are tryin

Re: Heads-up: hard reset of the 'staging' branch

Marius Bakke writes: > I have pushed a 'staging2' branch where I did the following: > > 1) git rebase -i --rebase-merges 8229ce3116c1f522c7157ab2dcd50dc2d765686a~ > > 2) Moved 8229ce3116c1f522c7157ab2dcd50dc2d765686a after > f00270d35a6ca814903a9392caedc29d44

Heads-up: hard reset of the 'staging' branch

Guix, I have good news and bad news. The good news is that the new commit verification infrastructure works great. 'make authenticate' will verify that all commits were signed by a key that was authorized by .guix-authorizations at that point in time. The bad news is that we need to ensure .gui

Re: Can we increase the print width/column in daemon backtraces

Pierre Neidhardt writes: > Ludovic Courtès writes: > >> Users are not supposed to see backtraces coming from the daemon or its >> helpers (‘guix substitute’, ‘guix offload’, etc.). > > How are we supposed to debug Guix daemon errors? You can run it directly from a shell, and/or attach a debugge

Staging freeze!

Guix, The 'staging' branch has seen plenty of changes recently and is now "frozen". Changes in the current iteration include Mesa 20.0.7, Rust 1.39 as the default Rust compiler, Qt 5.14.2, KDE Frameworks 5.70, updates and overhaul of all Vulkan packages, and lots of other minor changes. Testers

Release Guix 1.1.1?

Hello Guix, The installer has seen a few bugfixes since the 1.1.0 release, and guix-install.sh has also had a face lift. Not to mention the big "core-updates" merge that broke everyones fonts, but also brought goodies such as GNOME 3.34. What do y'all think about targeting a 1.1.1 release a few

Re: [PATCH] gnu: fontconfig: Add replacement with font-dejavu instead of gs-fonts.

zimoun writes: > On Wed, 20 May 2020 at 23:41, Marius Bakke wrote: > >> Missing fonts in the manual is another known issue and was not clear >> from your initial message: <https://issues.guix.gnu.org/issue/41418>. > > My initial message was on <http://issues.gu

Re: [PATCH] gnu: fontconfig: Add replacement with font-dejavu instead of gs-fonts.

Leo Famulari writes: > On Sun, May 17, 2020 at 04:50:12PM +0200, Marius Bakke wrote: >> This is a hack to make (some) fonts working when users don't have fonts >> specified in their system configuration, and (crucially) places where >> the fontconfig cache may be unavai

Re: [PATCH] gnu: fontconfig: Add replacement with font-dejavu instead of gs-fonts.

zimoun writes: > On Wed, 20 May 2020 at 15:55, Marius Bakke wrote: >> zimoun writes: > >> > Apparently, there is different fonts on master and core-updates, if yes >> > why? >> >> The only known difference since the core-updates merge is that >>

Re: [PATCH] gnu: fontconfig: Add replacement with font-dejavu instead of gs-fonts.

zimoun writes: > Apparently, there is different fonts on master and core-updates, if yes why? The only known difference since the core-updates merge is that applications using Pango (e.g. GTK+) no longer recognizes bitmap fonts. https://gitlab.gnome.org/GNOME/pango/issues/386 > I mean, on my

Re: [PATCH] gnu: fontconfig: Add replacement with font-dejavu instead of gs-fonts.

Leo Famulari writes: > On Sun, May 17, 2020 at 04:50:12PM +0200, Marius Bakke wrote: >> This is a hack to make (some) fonts working when users don't have fonts >> specified in their system configuration, and (crucially) places where >> the fontconfig cache may be unavai

Re: [bug#41382] [PATCH 0/6] Allow for a cryptographic hash function migration

Ludovic, (+ guix-devel) Ludovic Courtès writes: > Hello, > > Ludovic Courtès skribis: > >> Another option would be to create a data type that specifies >> its algorithm and its value. We’d replace the ‘sha256’ field with >> a ‘hash’ field of that type (in a backward-compatible way). Thinkin

[PATCH] gnu: fontconfig: Add replacement with font-dejavu instead of gs-fonts.

This fixes and . Reported by Pierre Neidhardt, W Knight, and others. * gnu/packages/fontutils.scm (fontconfig)[replacement]: New field. (fontconfig/font-dejavu): New variable. --- Guix, This is a hack to make (some) fonts working when users

Re: Out-of-date Mesa

Pierre Neidhardt writes: > Hi! > > I see that our Mesa 19.3.4 is out-of-date. 20.0.0 was released last February > and > 20.0.7 was released on May 14th: > > https://mesa3d.org/ The 'staging' branch has Mesa 20.0.7. > I'm wondering why a recent Mesa wasn't including in the last core-update > m

Re: core-updates all over again :)

Christopher Baines writes: > Hey, > > So, given that core-updates was recently merged, I guess it's time to > start the branch again? > > I've got two patches in mind, [1] for parallel xz compression during the > unpack phase if the build is happening in parallel, and [2] to enable > p11-kit in g

Re: Some packages failing to build

Guillaume Le Vaillant writes: > Guillaume Le Vaillant skribis: > >> Hi, >> >> After pulling guix with the merged core updates (guix at commit >> 95ffdfe86cb1b8a8e4fff1386a147718400b76e0), I found a few packages >> failing to build: >> >> - fbreader >> - gnubg >> - gnubik >> - postgis >> - p

core-updates merged!

Guix, The mythical 'core-updates' branch was just merged to 'master'! You will notice newer versions of many "core" packages such as glibc, findutils, make, etc; see 'guix pull --news' for the scoop. The mailing list has a (non-exhaustive) overview of the big changes this round: https://lists

Re: branch master updated: gnu: gnome-todo: Fix build.

Hi Danny, guix-comm...@gnu.org writes: > commit b17b29454d5edd61eecb4536461789b7a3865a9a > Author: Danny Milosavljevic > AuthorDate: Wed May 6 17:36:03 2020 +0200 > > gnu: gnome-todo: Fix build. > > * gnu/packages/patches/gnome-todo-delete-esource-duplicate.patch: New > file. >

Re: branch master updated: gnu: Add warsow-qfusion.

Pierre Neidhardt writes: > Marius Bakke writes: > >> On a related note, the 'ccl' package has a similar issue, and actually >> produces an invalid derivation on aarch64 and armhf. It can be seen by >> running e.g. 'guix weather -s armhf-linux'.

Re: branch master updated: gnu: Add warsow-qfusion.

Pierre Neidhardt writes: > Marius Bakke writes: > >>>> + (let ((commit "c4de15df559410aff0ca6643724e24cddb0ecbbd") >>>> +(arch (match (or (%current-target-system) >>>> + (%current-sy

Re: core-updates call for testing

Christopher Baines writes: > Marius Bakke writes: > >> Please try upgrading your profiles and systems and file bugs for >> anything that does not work for you. GNOME users in particular are >> encouraged to try the new GNOME 3.34 and report any regressions. > &g

Re: core-updates call for testing

Timothy Sample writes: > Hi Marius, > > Marius Bakke writes: > >> The "core-updates" branch is ready for testing! [...] >> >> Please try upgrading your profiles and systems and file bugs for >> anything that does not work for you. GNOME users

Re: branch master updated: gnu: Add warsow-qfusion.

Pierre Neidhardt writes: > Hi Marius, > > Sorry, I rebased and edited a few things, some changes slipped through > and resulted in this terrible commit :( > >> + (let ((commit "c4de15df559410aff0ca6643724e24cddb0ecbbd") >> +(arch (match (or (%current-target-system) >> +

Re: branch master updated: gnu: Add warsow-qfusion.

Hi Pierre, guix-comm...@gnu.org writes: > commit 39f1806ca1d04b9aee70e897e06466aadbbee152 > Author: Pierre Neidhardt > AuthorDate: Thu Apr 9 15:56:42 2020 +0200 > > gnu: Add warsow-qfusion. > > * gnu/local.mk (warsow-qfusion): New variable. This commit message is weird. > --- > g

Re: [PATCH] website: Update sjd.se servers.

Simon Josefsson writes: > * website/apps/base/templates/donate.scm (donate-t): I've pushed this patch now: https://guix.gnu.org/donate/ Thank you! signature.asc Description: PGP signature

Re: core-updates call for testing

Ricardo Wurmus writes: > Leo Famulari writes: > >> I'm doing `guix pull --branch=core-updates`, with a `guix describe` of >> commit a533c5a183 (core-updates from 2 weeks ago), on Debian, in tmux, >> and I see this weird thing: >> >> -- >> substitute: updating substitutes from 'https://privat

Re: core-updates call for testing

Leo Famulari writes: > On Tue, Apr 28, 2020 at 03:17:06PM +0200, Marius Bakke wrote: >> Leo Famulari writes: >> >> > I reconfigured my Guix System based on core-updates, and afterwards I >> > was unable to login, either remotely over SSH, or on the Linux cons

Re: When installing pycurl through pip, linux/limits.h is missing from glibc

Josh Marshall writes: > `python3 -m pip install pycurl` fails due to glibc not being able to find > the header "linux/limits.h". I am aware that there is a "python-pycurl" > package in guix, but the above should still work. I think glibc is missing > a dependency on linux headers, but I'm not s

Re: core-updates call for testing

Leo Famulari writes: > I reconfigured my Guix System based on core-updates, and afterwards I > was unable to login, either remotely over SSH, or on the Linux console. Do you still have the logs from this attempt? Curious what caused login to fail. signature.asc Description: PGP signature

Re: core-updates call for testing

Efraim Flashner writes: > I have a package which currently depends on gfortran-5, although > gfortran-5 doesn't build on core-updates. > > efraimf@penguin2:~/workspace/guix-core-updates$ ./pre-inst-env guix build > --no-grafts -e '(@@ (gnu packages gcc) gfortran-5)' > substitute: updating substi

Re: core-updates call for testing

sirgazil writes: > This time, one of my packages in a custom channel failed with "no code for > (term ansi-color)" (the package definition: > https://gitlab.com/sirgazil/guix-channel-x/-/blob/master/sirgazil-x/packages/guile.scm#L13). > This is not a new package in my profile, I've been using

Re: core-updates call for testing

sirgazil writes: > On Fri, 24 Apr 2020 03:20:41 + sirgazil wrote > > > On Thu, 23 Apr 2020 23:24:23 + Marius Bakke > wrote > > > Hello Guix! > > > > > > The "core-updates" branch is ready for testing!

core-updates call for testing

Hello Guix! The "core-updates" branch is ready for testing! According to 'guix weather', the substitute coverage is slightly better than on "master" for x86_64. You can get it by running: guix pull --branch=core-updates Please try upgrading your profiles and systems and file bugs for anythin

Re: GNU Guix 1.1.0 released

Vincent Legoll writes: >> Another question, why is the VM image partitionned >> like that (root first, then EFI) ? It makes root >> partition resizing more painful than needed. > > This one's still bugging me though Not really an answer to your question, but you can safely delete the EFI partiti

Re: Jami: Bug source investigation

Jan writes: > Hello, > > so I tested Jami on core-updates and it didn't fix the bug > (https://git.jami.net/savoirfairelinux/jami-packaging/issues/63) > > Here's my work up to now, it is on wip-jami branch: > https://gitlab.com/kromka_chleba/jami-package-and-other-things-for-guix/-/tree/wip-jami

Re: branch wip-gnome3.34 created (now 1538791)

Hi Kei, guix-comm...@gnu.org writes: > kkebreau pushed a change to branch wip-gnome3.34 > in repository guix. > > at 1538791 gnu: libical: Enable introspection and Vala bindings. > > This branch includes the following new commits: > > new e8cccae gnu: adwaita-icon-theme: Update to 3.

Reproducibility of Qt packages

Hi Maxim, I noticed this nice commit: guix-comm...@gnu.org writes: > commit a4f1a7e2db22cd028fb514846c2791928b8734d3 > Author: Maxim Cournoyer > AuthorDate: Wed Apr 15 02:03:26 2020 -0400 > > gnu: linphoneqt: Fix reproducibility issue and improve description. > > * gnu/packages/lin

Re: Packaging Jami "progress"

Jan writes: > I get several merge conflicts when merging wip-jami into core updates. > The wip-jami is based on the current master, rebased a minute ago. > Is there a way to avoid this without pain? A git merge will merge all the commits, some of which are bound to cause conflicts. I will try t

Re: Packaging Jami "progress"

Jan writes: > Hello everybody, > > I recently tested Jami using the latest pjproject version - 2.10 which > was supposed to fix some strange bugs that are present only on Guix, > but it didn't. > https://git.jami.net/savoirfairelinux/jami-packaging/issues/63 > Jami developer - Sébastien Blin told

Re: native or not

Vincent Legoll writes: >> Making ‘groff’ native was the right thing to do (and please, keep >> fixing bugs like this! :-) but it has nothing to do with making >> packages smaller. > > Never will ? > > I'm not expecting package size to shrink, but package closure > (is that the right word) size to

Re: core-updates frozen!

Jan Nieuwenhuizen writes: >> For those unaware, this means that the set of trusted binaries at the >> root of the package graph from which everything else derives is only 60 >> MiB (on i686 and x86_64). The set no longer includes GCC, binutils, or >> glibc! > >> For more information, see janneke

Re: Cannot build guix from git due to .po file errors

Marius Bakke writes: > Ludovic Courtès writes: > >> Hi Vagrant, >> >> Vagrant Cascadian skribis: >> >>> e...@boldquot.po:4591: format specifications in 'msgstr[0]' are not a >>> subset of those in 'msgid_plural' >>

Re: Cannot build guix from git due to .po file errors

Ludovic Courtès writes: > Hi Vagrant, > > Vagrant Cascadian skribis: > >> e...@boldquot.po:4591: format specifications in 'msgstr[0]' are not a >> subset of those in 'msgid_plural' >> /gnu/store/p50cw1g05g566bkbr6ylcibqffhha8w4-profile/bin/msgfmt: found 1 >> fatal error > > What’s the message on

Re: core-updates frozen!

Jan Nieuwenhuizen writes: > Marius Bakke writes: > >> The branch currently represents 676 commits by 26 people. Some >> highlights from this round: >> >> * Guix runs natively on GNU/Hurd. >> * Guix System can be cross-compiled for foreign architectures. >&

  1   2   3   4   5   6   7   8   9   10   >