Hi Ricardo,
Ricardo Wurmus writes:
> Hi,
>
>>> I mounted the target disk (an SSD) at /mnt, made sure that the microSD
>>> card was inserted, unmounted, and available at /dev/mmcblk1, and then
>>> ran
>>>
>>>guix system init config.scm /mnt
>>>
>>> This was successful.
>>>
>>> Unfortunately,
Hi Vagrant,
> On 2022-03-02, Ricardo Wurmus wrote:
>> I got myself a rockpro64 board.
> ...
>> So I then decided to build my own system and install a new u-boot onto
>> the microSD card. Here’s the system I built:
> ...
>> (bootloader (bootloader-configuration
>>(bootloader
Hi,
>> I mounted the target disk (an SSD) at /mnt, made sure that the microSD
>> card was inserted, unmounted, and available at /dev/mmcblk1, and then
>> ran
>>
>>guix system init config.scm /mnt
>>
>> This was successful.
>>
>> Unfortunately, rebooting failed. There is seemingly no activity
I also have this problem. It forgets which profile I'm using or
something. I have to launch the profile manager and select the profile
for it to use.
Hi,
Cássio Tavares writes:
>1. If I submit an issue with a package request, does it take long for
>the package to be made available?
It can take quite some time when you don’t have someone to review the
package. You are welcome to send me issue numbers with your patches and
I’ll
On 2022-03-29, Cássio Tavares wrote:
> So, I'm looking into package definition, and I have a few questions to
> start:
>
>1. If I submit an issue with a package request, does it take long for
>the package to be made available?
This can be highly variable, unfortunately. There aren't
Unfortunately, every time after guix pull updating icedove I have to set
up icedove again.
Opening icedove the path is set to:
/gnu/store/0vyrq4fz1wwxpy2izvjbrkfpaap5r5m9-icedove-91.7/bin/icedove
the only way to open icedove is to choose in the starter app an older
version: in my case:
Hi there!
I've been struggling with Guix for about three months now, but I still
couldn't get it working as I need it. I will need help on many fronts. One
of the problems is that the Guix ecosystem is still somewhat limited. I
know that there is a way to install Nix packages, but since I became
Hi Roland, hello Guix,
Roland Everaert via writes:
> Since I have updated my fedora box from version 34 to version 35, the
> libry path is messed up and most applications installed via dnf
> (fedora package manager) does not run.
>
> In a terminal (only xterm works so far), starting one of
TK writes:
> After some more investigation, I think I narrowed down the
> issue. Package texlive-inconsolata indeed installs the `t1-zi4r-0'
> font. However, the `map' for that font exists only under dvips, not in
> the pdftex subdir.
We’re generating these map files based on the contents of
> On Wednesday, March 23rd, 2022 at 9:58 AM, Ricardo Wurmus rek...@elephly.net
> wrote:
>
> > TK tkp...@protonmail.com writes:
> >
> > > `!pdfTeX error: pdflatex (file t1-zi4r-0): Font t1-zi4r-0 at 540 not
> > > found`
> > >
> > > A web search reveals that t1-zi4r-0 is an inconsolata font, but
On Wednesday, March 23rd, 2022 at 11:02 AM, TK wrote:
> On Wednesday, March 23rd, 2022 at 9:58 AM, Ricardo Wurmus rek...@elephly.net
> wrote:
>
> > TK tkp...@protonmail.com writes:
> >
> > > `!pdfTeX error: pdflatex (file t1-zi4r-0): Font t1-zi4r-0 at 540 not
> > > found`
> > >
> > > A web
12 matches
Mail list logo
