Hi Ludo',
I wanted to let you know that I have figured out what the failure is, and it
turned out to be a customization buried within some shared operating-system
configuration that I had forgotten about (and wasn't finding because it was due
to a missing import, and simply grepping for
Hi Ludo',
On Monday, May 13th, 2024 at 3:14 AM, Ludovic Courtès wrote:
>
>
> Hi Kaelyn,
>
> Kaelyn kaelyn.al...@protonmail.com skribis:
>
> > I recently updated my systems after finally finding
> > https://issues.guix.gnu.org/70051 and seeing the issue I was having with
> > booting with a
Hi Ludo' and others,
I recently updated my systems after finally finding
https://issues.guix.gnu.org/70051 and seeing the issue I was having with
booting with a non-root LUKS partition configured had been fixed. After
updating to a commit past these two:
49f82fca41 mapped-devices: luks:
Hi Maxim,
On Sunday, December 17th, 2023 at 2:15 PM, Maxim Cournoyer
wrote:
>
> Hello,
>
> Kaelyn kaelyn.al...@protonmail.com writes:
>
> > As a bit of followup, this bug still exists with the latest
> > core-updates commit. This not only affects i686 systems, but also some
> > x86_64
The manifest files have been fixed in mesa to include the path to the vulkan
layer shared objects in commit 02995444dbe9861c32b6e2cdbfb7a7b2affe2c2b.
--- Original Message ---
On Friday, May 5th, 2023 at 8:59 PM, John Kehayias
wrote:
>
>
> Hi Kaelyn,
>
> On Thu, May 04, 2023 at 11:45 PM, Kaelyn wrote:
>
> > --- Original Message ---
> > I wasn't sure the best place to share it, so I've attached my "run"
> > script for
--- Original Message ---
On Thursday, May 4th, 2023 at 9:50 PM, John Kehayias
wrote:
> > I have similar use cases of FHS containers to run binaries (primarily
> > games). I recently ran into the issue of gcc:lib going away and no
> > output from a visible package providing libstdc++. My
Hi,
--- Original Message ---
On Thursday, May 4th, 2023 at 3:26 PM, John Kehayias
wrote:
>
> Hi Christopher,
>
> On Thu, May 04, 2023 at 11:05 AM, Christopher Rodriguez wrote:
>
> > Sorry for the spam; Resending this without the bugs address, but with
> > the issue's address.
> >
>
As a bit of followup, this bug still exists with the latest core-updates
commit. This not only affects i686 systems, but also some x86_64 packages like
wine/wine64 which require a 32-bit build in addition to a 64-bit one.
Here is a revised diff with comments added for the flags.
diff --git a/gnu/packages/libreoffice.scm b/gnu/packages/libreoffice.scm
index 8343f8ffc6..ea7f0f19e9 100644
--- a/gnu/packages/libreoffice.scm
+++ b/gnu/packages/libreoffice.scm
@@ -1235,6 +1235,12 @@ (define (install-appdata app)
Hi,
>From some local testing, it appears the timestamps in bpmn.otg can be
>addressed by adding "otg" to the list of file extensions the existing
>'reset-zip-timestamps phase looks for:
diff --git a/gnu/packages/libreoffice.scm b/gnu/packages/libreoffice.scm
index 8343f8ffc6..69319177db 100644
Sorry, I messed up the patch a little as I wanted to get the error message that
prompted adding "--without-galleries". It should be:
diff --git a/gnu/packages/libreoffice.scm b/gnu/packages/libreoffice.scm
index 8343f8ffc6..7fb3fe1327 100644
--- a/gnu/packages/libreoffice.scm
+++
Hi,
I was able to build libreoffice for i686-linux by adding "--enable-lto" and
"--without-galleries" to the configure flags. The former seemed to resolve the
linking issue, and the latter was to deal with the build failing because of 0
themes being found.
That error was:
[build GAL]
I've just created https://issues.guix.gnu.org/59453 with the patch to mesa on
core-updates to fix the library paths in the Vulkan layer manifests. I split
the change out from my previous mesa update patch
(https://issues.guix.gnu.org/58566) as mesa on core-updates has since been
updated to
Hi,
I recently encountered the same error with mpv 0.35 on X11, and can confirm
that the patch in https://issues.guix.gnu.org/59378 fixes the playback error.
Cheers,
Kaelyn
Hi,
Trying to build 'wine-minimal for x86-64 on core-updates, the following error
is hit while building 'file for i686-linux:
/tmp/guix-build-file-5.42.drv-0/file-5.42/src/.libs/file: symbol lookup error:
/gnu/store/wb8f0ydwl7458ixgsmx65x5ni54c7zgk-glibc-mesboot-2.16.0/lib/libpthread.so.0:
I've just sent in https://issues.guix.gnu.org/58566 to update mesa on
core-updates, and that patch includes a new phase to fix up the Vulkan layer
manifests similar to how I'd done for vulkan-validationlayers in
https://issues.guix.gnu.org/57297.
When attempting a mass "guix refresh -ru" of system and home profile packages,
some bogus updates were encountered. One category of those is older/multiple
versions of a package all being updated to the latest, as was seen with gtk+@2,
libsigc++@2, and the gtkmm packages. For example:
$ guix
On Wednesday, May 25th, 2022 at 3:04 AM, Ludovic Courtès wrote:
> Hi Kaelyn,
>
> Kaelyn kaelyn.al...@protonmail.com skribis:
>
> > Recently I upgraded my server running bitlbee for the first time in a few
> > weeks (from guix commit 3363f2c878 to 14384d9586), and after rebooting I
> > was
Hi,
Recently I upgraded my server running bitlbee for the first time in a few weeks
(from guix commit 3363f2c878 to 14384d9586), and after rebooting I was unable
to connect to bitlbee because the child service spawned on connect terminates
within a few seconds. I'm not certain, but I believe
Hi,
‐‐‐ Original Message ‐‐‐
On Wednesday, July 21st, 2021 at 1:08 AM, Chris Marusich
wrote:
> Hi,
>
> I need a little help figuring out how to use gdb in Guix for bug 48941:
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=48941
>
> Here's the situation. A libfaketime test hangs
21 matches
Mail list logo
