On Mon, Sep 02, 2024 at 05:12:22PM +0200, Remco van 't Veer wrote:
> The issue is here:
>
> https://gitlab.gnome.org/GNOME/pygobject/-/issues/624
>
> I've tried and upgrading python-pygobject from 3.47.0 (currently on
> master) to 3.48.2 (current upstream release) fixes the issue.
Aha, thanks
While testing the recent kernel updates [0], I noticed that all builds
on the 'kernel-updates' branch fail on aarch64-linux:
https://ci.guix.gnu.org/eval/1528394?status=failed
As shown in the build log for linux-libre-5.4.281 [1], the tests fail:
--
finished 56 files: 5 errors
I basically agree with you :)
On Mon, Jul 29, 2024 at 09:21:57PM -0400, Richard Sent wrote:
> Breaking changes are okay, and if we consider this too niche of a use
> case or too high of a maintenance burden it should be dropped. I do
> believe it should progress into the consideration stage instea
On Mon, Jul 29, 2024 at 11:00:36AM -0400, Richard Sent wrote:
> For consideration, I know at least one 3rd-party channel relies on being able
> to create a multiarch container containing i686 packages. I'll refrain from
> linking since it packages nonfree software. This is an example where keepin
For a long time we've not been able to build linux-libre on i686-linux
because the source unpacking process runs out of memory.
I'm forwarding this bug to guix-devel to get more attention.
Is anybody actually using i686-linux anymore? Or should we begin to
officially remove support for it?
On Thu, Jul 11, 2024 at 04:23:09PM -0400, Leo Famulari wrote:
> Subject: [PATCH] WIP: Boost: Fix a bug that breaks libetonyek.
>
> This fixes <https://issues.guix.gnu.org/72040>
>
> * gnu/packages/patches/boost-fix-duplicate-definitions-bug.patch: New file.
> * gnu/l
Thank you Ricardo! I was totally stuck on this.
On Mon, Jul 22, 2024, at 05:29, Ricardo Wurmus wrote:
> This is now fixed in commit bdff6baca39a73b3cfc5400e117795cad0c180cf.
>
> dbus-daemon watches XDG_* directories, and it bailed out because the
> list of directories to watch is just too large.
On Mon, Jul 15, 2024 at 07:38:11PM -0400, Leo Famulari wrote:
> It's weird that dbus is killed by signal 11, SIGSEGV.
>
> I see that some other package manually start dbus for the test suite, so
> I'll try my hand at it.
Hm, I didn't make any progress with this. Doe
On Sun, Jul 14, 2024 at 01:52:37PM -0400, Leo Famulari wrote:
> I reported this problem upstream:
>
> https://gitlab.gnome.org/GNOME/epiphany/-/issues/2392
The GNOME team suggests that we make sure that dbus is running in the
build environment, and indeed it seems there is something
I reported this problem upstream:
https://gitlab.gnome.org/GNOME/epiphany/-/issues/2392
For some reason, mumi doesn't display the message
I sent about this bug, but only the attachment. It does display on
. In any case, here is the original message:
On core-updates commit 378e1d9b69b030, Epiphany (the GNOME web browser)
fails its test suite. Specifically, several of its tests fail l
I was holding it wrong. icu4c-73 and icecat are fine on core-updates.
Sorry for the noise!
On core-updates commit dd9660264b39b. the icu4c-73 package fails its
tests like this:
--
make[2]: Leaving directory
'/tmp/guix-build-icu4c-73.1.drv-0/icu/source/test/cintltst'
-
| *** FAILING TEST SUMMARY FOR: intltest
TestHebrewCalendarInTemporalLeapYe
On Sat, Jul 13, 2024 at 01:39:21PM -0400, Leo Famulari wrote:
> There is some discussion on the Libreoffice mailing list, but so far
> it's inconclusive from my perspective. But if I understand correctly,
> their recommended solution would be to create a source origin of
> Boost
On Thu, Jul 11, 2024 at 04:23:09PM -0400, Leo Famulari wrote:
> Here's a patch that patches Boost, while also creating a hidden package
> boost-for-source-highlight. This variant is only used by the
> source-highlight package, which is used by gdb, and thus rust. So, it
> aims to
On Thu, Jul 11, 2024, at 11:32, Leo Famulari wrote:
> On Thu, Jul 11, 2024 at 11:25:34PM +0800, Zheng Junjie wrote:
>> > So, it's a problem with cmake?
>> >
>> > Do you know if they've fixed it in later versions?
>>
>> see https://gitl
On Thu, Jul 11, 2024 at 03:15:27PM -0400, Leo Famulari wrote:
> I'm testing a patch for Boost now. It will cause a huge number of
> rebuilds, so it would be great to come up with another approach.
Here's a patch that patches Boost, while also creating a hidden package
boost-for-
I found the bug report, which is for Boost:
https://github.com/boostorg/phoenix/issues/111
Basically, versions 1.81 through 1.83 exhibit this defect.
I'm testing a patch for Boost now. It will cause a huge number of
rebuilds, so it would be great to come up with another approach.
On Thu, Jul 11, 2024 at 12:00:56PM -0400, Leo Famulari wrote:
> I think this upstream report (closed without resolution) describes the
> problem:
>
> https://bugs.documentfoundation.org/show_bug.cgi?id=152569
I sent a report to the mailing list where build failures are supposed to
I think this upstream report (closed without resolution) describes the
problem:
https://bugs.documentfoundation.org/show_bug.cgi?id=152569
Boost 1.81 (and presumably 1.83, which we have on core-updates) is not
compatible with the libetonyek code.
On Thu, Jul 11, 2024 at 11:32:53AM -0400, Leo Famulari wrote:
> Okay, great. I confirm your patch fixes the problem. I'll push it to
> core-updates on your behalf.
Pushed as 50243774824597dbd141a074a7be0117dc450cef
Thanks for your help!
signature.asc
Description: PGP signature
On Thu, Jul 11, 2024 at 11:25:34PM +0800, Zheng Junjie wrote:
> > So, it's a problem with cmake?
> >
> > Do you know if they've fixed it in later versions?
>
> see https://gitlab.kitware.com/cmake/cmake/-/issues/25200
Thanks!
> > Would this remove zlib support from openimageio?
>
> no, just fix
On Thu, Jul 11, 2024 at 02:29:59PM +0800, Zheng Junjie wrote:
> see patch, as i known, because ours cmake too old, have a bug about zlib.
So, it's a problem with cmake?
Do you know if they've fixed it in later versions?
> + #:phases #~(modify-phases %standard-phases
> +
On core-updates commit 378e1d9b69b030, Epiphany (the GNOME web browser)
fails its test suite. Specifically, several of its tests fail like this:
--
>>> G_TEST_BUILDDIR=/tmp/guix-build-epiphany-44.8.drv-0/build/tests
>>> GSETTINGS_SCHEMA_DIR=/tmp/guix-build-epiphany-44.8.drv-0/build/data
>>>
On core-updates commit 378e1d9b69b030a165, openimageio fails to build
like this:
--
[ 30%] Building CXX object
src/libOpenImageIO/CMakeFiles/OpenImageIO.dir/imageio.cpp.o
cd /tmp/guix-build-openimageio-2.5.13.0.drv-0/build/src/libOpenImageIO &&
/gnu/store/86fc8bi3mciljxz7c79jx8zr4wsx7xw8-gcc
On core-updates commit 378e1d9b69b030a, python-gst fails its test suite
like this:
--
==
FAIL: testPropertyMarshalling (test_types.TestFraction)
--
Traceback
On Thu, Jul 11, 2024 at 02:00:45AM +0800, Zheng Junjie wrote:
> i think just disable this test, see
>
> https://invent.kde.org/frameworks/ki18n/-/commit/241e0cfa96b1491721f361f1713b3514c58bde56#note_654140
> https://gitweb.gentoo.org/proj/kde.git/commit/?id=28525d897f1a83a81df0bbc3ff08de8d94083617
On core-updates commit 736939037346, libetonyek fails to build like
this (sorry in advance for the long lines, full log attached):
--
CXXLDlibetonyek-0.1.la
On core-updates commit 736939037346, ki18n fails its test suite like
this:
* Start testing of KCatalogTest *
Config: Using QtTest library 5.15.10, Qt 5.15.10 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 11.4.0), unknown unknown
PASS : KCatalogTest::initTestC
I messed up this report so I'm closing it and will open a new one. I
think it will be too confusing to leave this report open as it is.
On core-updates commit 736939037346, libetonyek fails its test suite
like this:
--
* Start testing of KCatalogTest *
Config: Using QtTest library 5.15.10, Qt 5.15.10 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 11.4.0), unknown unknown
PASS : KCatalogTes
On Sun, Jun 23, 2024 at 10:39:18AM +0200, Liliana Marie Prikler wrote:
> Note: Security bugs should go to guix-security instead. But thanks for
> pointing out the new Emacs release, I've pushed an update. (Thus
> marking this done)
I think that only secret security bugs should go to guix-security
On Mon, Jun 10, 2024 at 08:30:32AM +, Guillaume Le Vaillant wrote:
> On an IPv6-only network, the default configuration for ntp-service-type
> doesn't work, because the default pool used (<0.guix.pool.ntp.org>)
> doesn't have IPv6 addresses.
>
> In fact, the <1.guix.pool.ntp.org> and <3.guix.p
On Thu, Apr 11, 2024 at 03:18:49PM -0400, Leo Famulari wrote:
> I sent a patch:
>
> https://issues.guix.gnu.org/issue/70343
This should be fixed with commit cc38699cf0cfd804a43ca1b6c8602cfc84e06117
Please let us know if you see more problems. Thanks for the report!
On Thu, Apr 11, 2024 at 10:55:39AM -0400, Leo Famulari wrote:
> Okay, thanks for looking. We can add a dependency on python-pyyaml and
> it should work.
I sent a patch:
https://issues.guix.gnu.org/issue/70343
And CI will test it here:
https://ci.guix.gnu.org/eval/1241100
On Thu, Apr 11, 2024 at 04:42:27PM +0200, Tomas Volf wrote:
> I would assume it is the texinfodocs triggering the YNL_INDEX for us. This
> snippet from the commit message:
>
> If one of other targets such as latexdocs or epubdocs is built
> without building htmldocs, missing .rst files can ca
On Wed, Apr 10, 2024 at 05:05:15PM +0200, Tomas Volf wrote:
> linux-libre-documentation is broken again:
>
> starting phase `build'
> Traceback (most recent call last):
> File
> "/tmp/guix-build-linux-libre-documentation-6.8.4.drv-0/linux-6.8.4/./tools/net/ynl/ynl-gen-rst.py",
> li
I just saw this on Debian:
--
$ guix shell -D guix -- ./pre-inst-env guix weather linux-libre
computing 1 package derivations for x86_64-linux...
looking for 1 store items on https://ci.guix.gnu.org...
guix weather: warning: substitutes from 'https://ci.guix.gnu.org' are
unauthorized
hint: To
On Sun, Mar 17, 2024 at 09:39:12AM -0700, Zacchaeus Scheffer wrote:
> Hi all,
>
> I know this isn't a properly submitted patch, but I think the change is
> pretty simple. 2024 taxes are comming up in the US. Could someone bump
> the version number for opentaxsolver? I tested the following chang
Can you share the error messages here?
On Thu, Feb 22, 2024, at 09:13, Gabriel Wicki wrote:
> linux-libre-documentation fails to build (see
> https://ci.guix.gnu.org/build/3512631/details)
Pushed as 877abbdae790deaacf30af8a845e2290c39e10ff
On Fri, Feb 09, 2024 at 09:28:14PM +0100, Wilko Meyer wrote:
> * gnu/packages/aux-files/linux-libre/6.7-arm.conf,
> gnu/packages/aux-files/linux-libre/6.7-arm64.conf: Add platform support.
Thanks! Pushed to 'kernel-updates' along with the latest releases.
On Thu, Feb 08, 2024 at 07:57:38AM +0100, Wilko Meyer wrote:
> Vagrant Cascadian writes:
>
> > [[PGP Signed Part:Undecided]]
> > The linux-libre 6.7.x package contains ... as far as I can tell, no
> > supported arm64/aarch64 platforms! This is a pretty significant
> > regression from the linux-li
After 4 years, many upstream releases of mpv and FFmpeg, and a new
laptop, I'm closing this bug as "not actionable".
As reported on #guix by jeremyc [0], the standard method for calculating
the hash of a Git checkout is not working as expected for the Erlang
package [1].
Currently, our Erlang package has this source block:
--
(version "25.3.2")
(source (origin
(method git-fetch)
I see that ci.guix.gnu.org's builders seem to run out of memory while
building kernel headers for i686-linux:
--
xz: (stdin): Cannot allocate memory
/gnu/store/ns71xxkb3fzr37934bim9l8xiv68kc7w-tar-1.34/bin/tar:
/gnu/store/536ifp75wv8i1kb1k0szv7zd57ygpg0n-linux-libre-6.5.13-guix.tar.xz:
Wrote
On Tue, Nov 14, 2023 at 12:11:14AM -0500, Leo Famulari wrote:
> On Tue, Oct 31, 2023 at 01:29:00AM +0100, Wilko Meyer wrote:
> > * gnu/packages/linux.scm (linux-libre-6.6-version,
> > linux-libre-6.6-gnu-revision,
> > deblob-scripts-6.6, linux-libre-6.6-pristine-source, l
On Tue, Oct 31, 2023 at 01:29:00AM +0100, Wilko Meyer wrote:
> * gnu/packages/linux.scm (linux-libre-6.6-version,
> linux-libre-6.6-gnu-revision,
> deblob-scripts-6.6, linux-libre-6.6-pristine-source, linux-libre-6.5-source,
> linux-libre-headers-6.6, linux-libre-6.6): New variables.
> * gnu/packa
On Thu, Nov 09, 2023 at 03:57:36PM +0100, Wilko Meyer wrote:
> * gnu/packages/linux.scm (linux-libre-6.6-version,
> linux-libre-6.6-gnu-revision,
> deblob-scripts-6.6, linux-libre-6.6-pristine-source, linux-libre-6.5-source,
> linux-libre-headers-6.6, linux-libre-6.6): New variables.
> * gnu/packa
On Mon, Nov 06, 2023 at 11:41:47PM +0100, Wilko Meyer wrote:
> Agreed, thanks for mentioning this! I'll send a v3 of this patch series
> that splits up the changes in two commits; one introducing 6.6, the
> other making it the default kernel (which can be applied after a couple
> of days if 6.6 wor
On Wed, Nov 01, 2023 at 03:32:27PM +0100, Wilko Meyer wrote:
> * gnu/packages/linux.scm (linux-libre-6.6-version,
> linux-libre-6.6-gnu-revision,
> deblob-scripts-6.6, linux-libre-6.6-pristine-source, linux-libre-6.5-source,
> linux-libre-headers-6.6, linux-libre-6.6): New variables.
> * gnu/packa
On Wed, Nov 01, 2023 at 03:32:27PM +0100, Wilko Meyer wrote:
> * gnu/packages/linux.scm (linux-libre-6.6-version,
> linux-libre-6.6-gnu-revision,
> deblob-scripts-6.6, linux-libre-6.6-pristine-source, linux-libre-6.5-source,
> linux-libre-headers-6.6, linux-libre-6.6): New variables.
> * gnu/packa
On Mon, Oct 30, 2023 at 11:26:55PM +0100, Wilko Meyer wrote:
> * gnu/packages/linux.scm (deblob-scripts 5.10): Update hash.
Pushed as e3f318f0489322c4c9b5964f03a8b063a7bfbebd, thanks!
On Mon, Oct 30, 2023 at 11:26:51PM +0100, Wilko Meyer wrote:
> Wilko Meyer (4):
> gnu: deblob-scripts 6.5: Update hash.
> gnu: deblob-scripts 6.1: Update hash.
> gnu: deblob-scripts 5.15: Update hash.
> gnu: deblob-scripts 5.10: Update hash.
Thanks! I pushed patches 2 through 4 to 'kernel-
Fixed with commit 8b8607a9452b7690b15f7db2613abdc211d40cee
I see, thanks for the explanation!
On Mon, Aug 28, 2023, at 18:40, Maxim Cournoyer wrote:
> tags 65585 + notabug
> quit
>
> Hi Leo,
>
> Leo Famulari writes:
>
>> With a `guix describe` like this, I'm unable to build Guix from a fresh Git
>> checkout of the m
With a `guix describe` like this, I'm unable to build Guix from a fresh Git
checkout of the master branch.
--
guix 985638a
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 985638aea14720e16ed5fd94a0e1382a57dec7ac
--
--
$ guix shell --pur
The update of rxvt-unicode to version 9.31 brought a bug that causes the
prompt in new terminal instances to be placed in the middle of the
window and not at the top.
Reported upstream:
http://lists.schmorp.de/pipermail/rxvt-unicode/2023q1/002639.html
Also reported at Arch with a patch to fix it
I noticed this inconsistency:
--
$ ls -l /var/log/messages*
-rw-r- 1 root root 112994 Jul 10 14:29 /var/log/messages
-rw-r--r-- 1 root root 8883 Jul 5 12:00 /var/log/messages.1.gz
--
This seems like a mistake.
On Wed, Mar 15, 2023 at 10:02:20PM -0400, Maxim Cournoyer wrote:
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> Throw to key `guile-ssh-error' with args `("write_to_channel_port"
> "Parent session is not connected" # 7fca183c31c0> #f)'.
> --8<---cut here---end--
Can someone help me by pointing to the original discussion of this
change?
On Sat, Apr 22, 2023 at 04:03:29PM +, Kyle Andrews wrote:
> I'm filing this bug report since I'm worried that the people who are most
> knowledge about Go in Guix might not check that mailing list as frequently.
I might be part of that group of people in Guix that pays attention to
Go. Howev
On Tue, Apr 04, 2023 at 07:31:47PM +0200, Simon Tournier wrote:
> Maybe I am doing something wrong, I get:
>
> --8<---cut here---start->8---
> $ guix refresh -l gnupg | cut -f1 -d':'
> Building the following 1491 packages would ensure 2880 dependent packages are
On Mon, Mar 20, 2023 at 09:01:33AM -0400, Ethan Blanton via Bug reports for GNU
Guix wrote:
> However, the bug referenced here is fixed in upstream commit
> 4cc724639c012215f59648cbb4b7631b9d352e36, which shipped in gnupg
> 2.2.34. Meanwhile, all gnupg releases older than 2.2.35 suffer from
> an
On Tue, Apr 04, 2023 at 11:48:31AM +0200, Simon Tournier wrote:
> On Mon, 20 Mar 2023 at 09:01, Ethan Blanton via Bug reports for GNU Guix
> wrote:
> > I believe the pin on 2.2.32 can be lifted, but as gnupg is important
> > infrastructure I am unsure about directly submitting a patch to update
>
- Forwarded message from Philip Nelson -
Date: Tue, 28 Mar 2023 04:42:25 +
From: Philip Nelson
To: guix-de...@gnu.org
Subject: Contributing guide building from git make check failure
I've been following the Contributing guide "Building from Git" section (
https://guix.gnu.org/manual
On Mon, Feb 27, 2023 at 08:40:36AM -0500, Maxim Cournoyer wrote:
> This should allow you to proceed as usual:
[...]
Thanks! I've prepared the patch, availabe as part of this patch series:
https://issues.guix.gnu.org/61947
On Sat, Feb 25, 2023 at 11:23:13PM -0500, Maxim Cournoyer wrote:
> It's indeed been applied upstream. Can't we just drop our local version
> of it?
Do I need to set the 'doc-supported?' value somehow for particular
kernel versions? It would be helpful for me if you could try it, if this
stuff is
On Wed, Nov 16, 2022 at 11:55:51AM -0500, Maxim Cournoyer wrote:
> .../patches/linux-libre-infodocs-target.patch | 88 ++
This patch doesn't apply to linux-libre 6.2.1, as shown below. If I
understand correctly, it's been applied upstream, but I don't understand
how to adjust things on our en
Thanks for the report!
Did you follow the instructions about X.509 Certificates in the manual
section Application Setup? That section is about using Guix on other
distros.
I use vdirsyncer from Guix on Debian and it works fine when validating
X.509 / TLS / HTTPS certificates.
There's a serious vulnerability in NSS:
"An attacker could construct a PKCS 12 cert bundle in such a way that
could allow for arbitrary memory writes via PKCS 12 Safe Bag attributes
being mishandled."
https://www.mozilla.org/en-US/security/advisories/mfsa2023-06/#CVE-2023-0767
Apparently it is f
Thanks for the report!
On Tue, Feb 14, 2023 at 09:27:31PM +, tmikew1985 via Bug reports for GNU
Guix wrote:
> Output from guix pull:
>
> Updating channel 'guix' from Git repository at
> 'https://git.savannah.gnu.org/git/guix.git'...
> Authenticating channel 'guix', commits 9edb3f6 to a22b62
On Sun, Jan 22, 2023 at 10:36:21PM +0100, Ludovic Courtès wrote:
> $(guix time-machine --commit=9923100a42ffa80f604c1c13a5e999e6a4c15146 \
> -- system vm gnu/system/examples/bare-bones.tmpl) -m 1024 # Bad!
I can reproduce.
It seems to work fine without '-m 1024', in which case it only has
On Tue, Jan 17, 2023 at 11:23:42AM +0100, Ludovic Courtès wrote:
> The file exists but it’s a dangling symlink:
>
> --8<---cut here---start->8---
> $ ls -l
> /gnu/store/12wnswvdc1mk9cr498dxflxim4qm2pyq-clang-toolchain-13.0.1/lib/libz.so.1.2.11
> lrwxrwxrwx 1 gu
On Thu, Jan 05, 2023 at 04:11:45PM -0500, Greg Hogan wrote:
> The recent zlib graft (from 1.2.11 to 1.2.12) is broken when grafting
> clang-toolchain. The symbolic link points to the correct directory but
> the incorrect file version.
> --8<---cut here---start->
On Mon, Jan 02, 2023 at 05:17:37PM -0500, Leo Famulari wrote:
> On Sun, Jan 01, 2023 at 09:34:15PM +0100, Liliana Marie Prikler wrote:
> > Am Sonntag, dem 01.01.2023 um 17:50 + schrieb Elias Kueny:
> > > Hello,
> > >
> > > I&#x
On Sun, Jan 01, 2023 at 09:34:15PM +0100, Liliana Marie Prikler wrote:
> Am Sonntag, dem 01.01.2023 um 17:50 + schrieb Elias Kueny:
> > Hello,
> >
> > I'm using Guix System and on Guix commit
> > 8f93a1e01a879ae026678dd92c18e2a2a49be540.
> > Building Glimpse fails during the configuration phas
I'm not able to create QR codes in Inkscape.
I try to create a QR code in Inkscape by going through these menus:
Extensions -> Render -> Barcode -> QR Code
But, when I click "Apply" to create the QR code, Inkscape prints an
error message like this:
--
Traceback (most recent call last):
Fil
On Fri, Jul 15, 2022 at 01:12:14PM -0400, Maxim Cournoyer wrote:
> Hi,
>
> Leo Famulari writes:
>
> > I notice that tests/publish.scm crashes consistently when run "by hand"
> > with `make check` on ci.guix.gnu.org:
> >
> > --
> > $ m
On Wed, Jul 13, 2022 at 11:11:49PM -0400, Maxim Cournoyer wrote:
> Hi Leo,
>
> Leo Famulari writes:
>
> > Since my last full upgrade on June 9 2020, I found that if I have
> > font-dejavu installed in my profile, my terminal (rxvt-unicode) no
> > longer
Fixed with commit 40a729a0e6f1d660b942241416c1e2c567616d4d
Between commits
2e0d02ebe351024cd97911cb1e5e1a6af1edc7f0..93baba64753d4f8543b38a3a6092b7a71b79b246,
the pytest2-cov package broke, which in turns breaks the important
package wicd.
https://ci.guix.gnu.org/build/791078/details
--
starting phase `build'
running "python setup.py" with command "b
It's not easy (perhaps impossible) to bisect the core-updates branch. That's
because most commits on the branch are not expected to build. For most of the
branch's lifetime, it's merely a place to dump patches that cause rebuilds of
the entire distro (e.g. a glibc update). It's only in the final
On Fri, Feb 11, 2022 at 04:03:03AM +0800, Squirrel via Bug reports for GNU Guix
wrote:
> It seems that this is a bug from upstream linux, which may be patched soon.
> Please see
> https://lore.kernel.org/stable/164448100914.10463.9523338503936670263.kv...@kernel.org/
Good news, this bug has been
On Tue, Feb 22, 2022 at 10:57:53PM -0700, Jesse Gibbons wrote:
> Calibre isn't displaying any text in its book view interface (see
> screenshot). Even after I delete all the calibre configuration files in
> .config and .local/share the problem persists. I do not know if this is
> specific to guix o
On Sat, Feb 19, 2022 at 09:39:52PM -0600, Jacob MacDonald wrote:
> That is the summary of what I know now; I'm also happy to copy the
> rest of the emails back into this thread, with Leo's permission.
That's fine with me.
On Thu, Feb 17, 2022 at 01:05:09AM -0600, Jacob MacDonald wrote:
> Calibre's main window is unaffected, but it's impossible to read any
> EPUBs in the viewer. The text in both the book and the settings is
> affected. Images show up.
>
> I don't remember if I noticed this before or after the bit Qt
On Wed, Feb 16, 2022 at 12:39:46AM +0800, Squirrel via Bug reports for GNU Guix
wrote:
> The patch for it has just been applied in the newest upstream kernel
> releases. (https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.23)
Are you sure the bug is fixed in 5.15.23?
I don't see anythin
On Mon, Feb 14, 2022 at 04:16:09PM +, Ahmad Draidi wrote:
> Running 'guix pull' on a fresh basic install of Guix System 1.3.0 for i686
> gets stuck at around 80%.
Okay, can you share the result of `guix describe` to confirm what
revision of Guix you're using?
Can you use strace to see what it
On Tue, Feb 15, 2022 at 03:56:27PM +0100, Ludovic Courtès wrote:
> 2022 has left me without a working Linux-libre kernel.
>
> Breakage occurred sometime between:
>
> • 92faad0adb93b8349bfd7c67911d3d95f0505eb2
> (Jan. 3rd; Linux-libre 5.15.12)
>
> • 43dd34ca212c99a97da7a2c237158faa9a1
On Fri, Feb 11, 2022 at 04:03:03AM +0800, Squirrel via Bug reports for GNU Guix
wrote:
> Blacklisting the iwlwifi kernel module works as a workaround for now, as is
> suggested by Jason Self, the maintainer of the Freesh and libeRTy apt
> repositories of linux-libre kernel. He mentioned it in Tris
I'm still experiencing this problem with 5.15.21, as well 5.16.7 and
5.4.177.
On Sun, Dec 19, 2021 at 09:35:52PM +0100, Vivien Kraus via Bug reports for GNU
Guix wrote:
> On master, I can’t reconfigure my system, because the linux-modules.drv
> fails with the following error:
[...]
> gnu/build/linux-modules.scm:257:5: kernel module not found "simplefb"
> "/gnu/store/1ai7m
On Tue, Feb 08, 2022 at 10:05:32PM +0100, Dr. Arne Babenhauserheide wrote:
> Hello Guix,
>
> I see strange conflicts when trying to update packages via manifest:
>
> guix package: error: profile contains conflicting entries for python-cffi
> guix package: error: first entry: python-cffi@1.15.0
On Tue, Feb 08, 2022 at 06:57:14PM -0500, Zacchaeus Scheffer wrote:
> Hi Guix!
>
> I came across some weird behavior with guix home. I wanted to recreate a
> working home environment from one machine on another (because I need a
> working qutebrowser install :3). I did this by doing "guix pull
>
On Tue, Feb 08, 2022 at 11:18:08AM +0100, Ludovic Courtès wrote:
> Unfortunately it seems that libgit2 doesn’t let us turn off certificate
> verification:
>
> https://libgit2.org/libgit2/#HEAD/group/libgit2
>
> ‘verify_server_cert’ in src/streams/openssl.c is called
> unconditionally.
Ah, that
On Mon, Feb 07, 2022 at 10:54:53AM -0600, Katherine Cox-Buday wrote:
> I thought I'd chime in with another data-point:
>
> - Lenovo ThinkPad T480s
> - Normal BIOS
> - Vanilla Linux kernel(s)
> - kernel v5.15.16 boots fine; everything after seems to hit this bug
> - Turning off bluetooth in BIOS se
On Sat, Feb 05, 2022 at 11:42:38PM -0500, Maxim Cournoyer wrote:
> FYI, I pushed this workaround in
> 3c3c9d259f87fbc8c1d9551af32e79f9f168f596.
I don't see this commit in the repo.
On Sat, Feb 05, 2022 at 08:22:32AM +0100, Liliana Marie Prikler wrote:
> Looking at the size of this thing compared to our audacity, I thought
> to myself "hmm, that's a shell script" and sure enough
>
> --8<---cut here---start->8---
> #!/gnu/store/4y5m9lb8k3qkb
On Fri, Feb 04, 2022 at 05:32:30PM -0500, Leo Famulari wrote:
> Audacity still does not keep a reference to FFmpeg, and it cannot
> Opus-encoded files (among many other types of encodings):
On #guix, lilyp found the culprit:
http://logs.guix.gnu.org/guix/2022-02-04.log#235737
... an ex
1 - 100 of 1398 matches
Mail list logo
