On 30/11/19 5:05 pm, Maciej W. Rozycki wrote:
> How do I do that though? There doesn't appear to be anything there I
> could do from my profile page or elsewhere.
Oh I was only thinking of something rudimentary like copying over the
list of pending patches into a text file.
> Sure, and
Some more analysis:
Creating a simple logger file:
$ cat logging.properties
handlers=java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level=ALL
I figured out a hacky intermediate solution shoftly after I wrote this
email, but never followed up.
Install Nix and the Nix service. Now I can hackily get a newer Node! ;)
Christopher Lemmer Webber writes:
> Our Node is out of date, but this may be fine security-wise and
> package-needs wise
On Thu, 28 Nov 2019, Siddhesh Poyarekar wrote:
> > Well, I've been using it to track the state my own patches submitted (and
> > during the period of my active MIPS GDB port maintenance also for other
> > people's submissions).
>
> Can you please take a snapshot of your state?
How do I do
I think the problem is that I was using an outdated version of `guix`. I
did a `guix pull` on my Guix system, the re-ran the command to build the
Docker image, and it works now.
One thing I noticed is that I have to pass the `--privileged` flag, or
subsequent invocations of `guix pull` fail with
Konrad Hinsen writes:
>> Maybe a "gfortran-toolchain" package with all the battery included?
>
> That sounds like a very good idea! And I even volunteer to
> implement it. Except if someone comes up with a better
> solution of course.
Here it comes:
