Hi Guix!
When building a system image for the pinebook pro, the image either
fails to build or fail to boot. This occurs when when using the
pinebook-pro-barebones-raw-image defined in the Guix repository.
When --system=aarch64-linux is not passed, the image build fails when
cross compiling
> What hardware do you have?
RYF certified IBM x200 with libreboot firmware.
Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz
16GB of RAM and 64GB of swap
4TB SSD and Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
-Jeremiah
Hi there,
I recently hit this issue, and was able work around it by:
1. Get root shell (via sudo or otherwise)
2. Disable dbus-system: 'herd stop guix-system'
3. Update guix: 'guix system reconfigure ...'
4. Reboot
Thought I would note it just in case its useful to someone else.
Kind regards,
May 10, 2024 at 1:51 AM, "Antonio Carlos Padoan Junior"
wrote:
>
> jbra...@dismail.de writes:
>
> >
> > May 9, 2024 at 1:53 PM, "Olivier Dion" wrote:
> >
> > The best place for bugs, is to discuss them on bug-guix@gnu.org. That way
> >
> > it ends up in our bug tracker.
Hello,
Ludovic Courtès writes:
> Hi,
>
> Marius Bakke skribis:
>
>> On the 'core-updates' branch, using copy-recursively on a nonexistent
>> directory does not cause a build failure. Instead an error is printed
>> and the script continues:
>>
>> (copy-recursively "doesnotexist" output)
>>
`guix challenge lilypond` now seems to pass, and "Created by FontForge
..." strings in emmentaler-*.svg files indeed indicate 1st Jan 1970.
I guess we can close the issue @Zimoun?
--
Best regards,
Nicolas Graves
I don't experience the issue anymore, closing it.
On 2023-03-17 13:49, Maxim Cournoyer wrote:
> Hi,
>
> Jack Hill writes:
>
>> On Thu, 16 Mar 2023, Nicolas Graves via Bug reports for GNU Guix wrote:
>>
>>>
