>A web-of-trust type approach is what I have previously heard discussed. In
>the context of such an approach, I have three things to say in support of
>my proposal.
>3. In those first two points, I claim some advantage relative to a
>web-of-trust style approach. However, both ideas are fully
>Once you've downloaded all the sources, if you ever need to rebuild on a
>different machine, you can reference these already downloaded sources,
>amiright? In effect, you've created own local mirror.
You can use nix-serve on the computer with the mirror, and then the
other computer will be
>Do I understand correctly that LLVM 3.3 (a Julia dependency)
>builds fine or fails on random without any specific changes that are
>obviously relevant to it? The failures are inside the test suite.
Just a data point: a local build failed (Hydra build, too), then one
local attempt
Hello
Do I understand correctly that LLVM 3.3 (a Julia dependency)
builds fine or fails on random without any specific changes that are
obviously relevant to it? The failures are inside the test suite.
___
nix-dev mailing list
>Oh, yes, another thing: independence of systemd :D
Oh? I currently have some weird NixPkgs-based init-less system, how do
I get NixOS services without systemd (or full NixOS without systemd as
PID 1, I am OK with systemd running as a daemon if it doesn't maange
logs and console sessions).
On 05/31/2015 11:33 AM, Peter Simons wrote:
I've been trying to make my NixOS re-use another machine's store
Substituting from a different machine is better done by setting
services.nix-serve.enable = true
and using it as a binary cache (at least I heard it's better).
It is better in the sense
I've been trying to make my NixOS re-use another machine's store, but
I've had no success. I've mounted the other machine's file system as
follows:
# mkdir /run/nix/remote-stores/other
# sshfs -o allow_root other:/ /run/nix/remote-stores/other
The other's /nix directory is visible:
# ls
If we're replacing bash we might as well go all the way...
Have we made any progress rewriting systemd in csh?
All the ways is at least Guile-as-a-shell, anf I guess we should just
admit that Guix with its dmd is the proper way forward?
I must admit that I don't like your defeatist attitude of
On Mon, Mar 30, 2015 at 9:47 PM, Ryan Trinkle ryan.trin...@gmail.com wrote:
On a somewhat related note, is there any way to see the exact
configuration.nix for a particular generation? It would be great to be able
to diff generations against each other (e.g.: to figure out whether a
channel
attached is a patch which fixes ecl, using the gmp and libffi supplied
by nix, preserving the dffi ecl feature.
Thanks, applied
Look at bittornado expression, for example, it sets PYTHONPATH for use
at runtime.
For ECL we need to set NIX_CFLAGS_COMPILE, I guess. Any flags in
attached are two patches:
1) to add mkcl, a common lisp implementation
Applied, thanks
2) to fix ecl, another common lisp implementation
I think adding a wrapper that sets NIX_CFLAGS_COMPILE and
NIX_CFLAGS_LINK is a better last-ditch solution than just forbidding
libffi (I don't remember if
I have question about Nix proper, independent of Nixpkgs or NixOS.
What kinds of attributes are appropriate as passthrough attributes on
a derivation set,
and which attributes are appropriate to be written out to the store in
a nix-support file?
Neither of these concepts exists outside of
I'm having an issue with the Julia Nix-expression[1]. I am trying to use it
together with the Julia package PyPlot[2] to plot figures with matplotlib. If
I try it in the command-line interface, then no plots show up. I only get a
textual representation of the figure objects. However, when I use
julia pygui(:qt); using PyPlot
Haven't yet launched X since your last email, but have you tried
pygui(:wx)?
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Firefox can simply be built — or just get its ELF header
edited — inside a chroot mimicking the layout you want by bind-mounting
/nix/ and then simply symlinking the libraries into /usr/lib. Here you
won't get any new determinism problems (or any non-trivial problems at
all).
Michael Raskin
Deterministic output means that something has to be done about profile-
guided optimistion. It is a subject of an old discussion in our
community as some people would like bit-perfect builds and others think
that PGO improves performance significantly and should be used.
In our case the main
I'm interested in using nix/nixos to build an application with its
full set of dependencies, and then deploy it to non-nixos machines as
a self-contained package (up to and including the system libraries),
without root privileges. Ideally I would like to not require that any
nix tools be
16596922mda_lv2.i686-linux
16591197mongodb.x86_64-linux
16599836qbittorrent.i686-linux
16599870qbittorrent.x86_64-linux
16590792syslogng_incubator.i686-linux
16604362
Previously we had configurations repository in SVN. I even continued to
update my configuration there long after Git migration. Its useful
function was that I could easily give a link like «see viric's
configuration».
I don't think comprehensiveness is that important for such a repository,
but
That's awesome idea. But I think we have to add lots of comments to this
examples (that help a lot while using live code). Or maybe just provide
some ideal configs with comments and other without them.
I think we need to throw some live configs like we had in SVN:
- nixos channel updates only when there are zero failures on jobset (this
would mean reverts will happen often - and I believe that's the correct way
to go instead of blocking people and punishing good testers)
Back to the good old times of any failure blocking channel update, m-m-m.
But
On Sat, Oct 25, 2014 at 05:45:34PM +0200, Nicolas Pierron wrote:
We have 2 solution, either we stop the regressions when a pull request
(PR) is made, or we stop it when the fire is in. The fireman role is
hard to keep, and we should be verifying as much as possible at the PR
time. Also, if
- IRC bot that reports build failures for a range of commits once
nixos-combined jobset is done
Would be nice
- email to commiters that broke the the build (with a range of commits and
list of builds failed)
Would be nice
- nixos channel updates only when there are zero failures on jobset
If this thing would be supported, this would give us a good reason to
push our nix expressions upstream. This would have at least 2 good
impacts:
- a growing awareness of nix
- a nice way for all developers to build their package
- Ease of integration of Nix-related tools thatt already come with
If you have systemd installed, then half of your Unix ecosystem is
locked into one particular implementation of services that used to be
diverse, modular, and replaceable.
They are still modular and replaceable (except for core stuff like udevd).
I think both we and you hyperbolize a bit.
For
Note that this proposal:
* reuses packages built for different environments (packages outputs
stay the same between boxes, it's boxes that change),
* doesn't generate a ton of wrappers by generating a wrapper for every
single package,
* gives a somewhat natural way to decide which options go
Does anyone mind if we (slowly) move binaries from $out/sbin to $out/bin?
Arguments for doing it:
1) The sbin vs bin distinction is an historic relic from the past. It
makes little sense on NixOS. (Even a normal (LSB-like) distro like
ArchLinux has already made the sbin - bin switch).
2) It's
build-use-chroot = true
build-chroot-dirs = /dev /proc /bin
So I have another problem ☺: packages relying on /bin/sh do not build
any longer. It looks that I cannot get my `build-chroot-dirs` option right.
build-chroot-dirs =
/bin=/nix/store/8qhilznm4abzjvnbkqi48zy6wrljgi80-bash-4.2-p45/bin
It sounds like a necessary evil.
Another option would be to make Hydra super fast... What has been explored
to optimize compile speeds? Using distcc, ccache, SSD, elastic scaling?
What if we had a security build fund that we could use to briefly run 500
machines to complete security builds?
- bossa: no idea
- saga: no idea
The only build was cancelled.
- guitone: no idea
First failure in ages is a cancelled build
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
I bet against our package set being buildable in 2 hours — because of
time-critical path likely hitting some non-parallelizable package.
I think most large projects can be compiled via distcc, which means that
all you need is parallel make.
WebKitGTK… (there is a comment about failure to make
With the awesome monitor.nixos.org system, we're prety close to 1) deriving
trivial patches (update version and sha256) automatically, 2) building
these trivial patches in a monitor.nixos.org-controlled branch, and 3)
notifying maintainers that a successful build of a new version exists so
they
1 not sure if 0.8.0.3 is relevant on linux
1 patch OK
2 hard to say
2 not linked on homepage
3 build failure
11 patch ok
12 build pending
23 irrelevant
29 no patch
What does no patch mean? (a new release without a patch or a tarball
But with a proper database implementation, perhaps it can do full text
indexing on its description, or indexing on the names, and proper
caching mechanisms as well.
Why reinvent the wheel?
Because every package is a piece of code in Nix programming language.
It's funny, for me it's the opposite - logging with systemd is sooo much better
than with Upstart. (IIRC, the logging of stderr of Upstart jobs was a
NixOS-specific hack, and other than that there was no logging support.)
Somehow, it work reliably…
However, there is a long-standing issue with
It's funny, for me it's the opposite - logging with systemd is sooo much
better
than with Upstart. (IIRC, the logging of stderr of Upstart jobs was a
NixOS-specific hack, and other than that there was no logging support.)
Somehow, it work reliably…
It did not. There was no way with
A program that takes v1.deb and v2.deb can output the list of patches added
and removed, as well as whether the meta-data for the package (scripts/* ?)
was changed.
This means that we switch to debian releases as our upstream?
For both of these packages it is fairly easy to generate a fully
However, there is a long-standing issue with stdout/stderr logging: if the
process dies before systemd has had a change to process its log message, then
systemd may not be able to figure out the unit corresponding to the message,
so
it may be lost (or not attributed to the unit). See
It did not. There was no way with Upstart to get the log output of a
service.
In NixOS the problem wasn't noticeable…
Again, the logging situation with systemd is vastly superior than it was with
Upstart. With Upstart you simply couldn't do something like systemctl status
foo.service and
I would like to add I absolutely love systemd, as it provides proper
dependency management, helping immensely for more dynamic setups where
hardware changes should trigger services reconfiguration, or for
changing services/vpn/routing based on wifi access point and more.
It's really nice that -
This post (to this ML) says pretty much what I think about systemd and
why I hate it:
http://article.gmane.org/gmane.linux.distributions.nixos/13967
I take these things more as a joke. It is even more extreme than to say
that KDE or GNOME is eating all desktop apps. To me systemd seems
As a sysadmin, I love systemd and journald. If you want to maintain lots of
disparate things and look all over the OS while troubleshooting, good for
you, but systemctl and journalctl make life so much easier. Upstart is a
very poor substitute.
What are the keys for journalctl to make it work?
On Tue, Sep 2, 2014 at 12:26 AM, Michael Raskin 7c6f4...@mail.ru wrote:
As a sysadmin, I love systemd and journald. If you want to maintain lots of
disparate things and look all over the OS while troubleshooting, good for
you, but systemctl and journalctl make life so much easier. Upstart
Shea Michael: By default systemd sends stdout stderr to the journal,
this is controlled by DefaultStandardOutput DefaultStandardError in
systemd-system.conf. So yes, if these are set to `journal` (or stdout is
set to `journal` and stderr to `inherit`) and you had stdout/stderr
messages which
How do people feel about this? Is it something I should maintain
independently of nixpkgs or does it belong in the main repo?
... please keep it out of the main Nixpkgs, at least for now. Reason
is that currently Nix performance drops linearly with the number of
packages. Until we have a
, Michael Raskin wrote:
On 31 August 2014 18:27, Michael Raskin 7c6f4...@mail.ru wrote:
I'd say, though, that only name-based operations drop in performance
that way…
Although for some strange reason we still recommend this way of using
Nix.
Nix newb asks: what would be the superiour alternative
Actually I think people are much more inclined to sit down and spend a
few minutes sometimes updating a package or two from their group rather
than putting their own name down specifically on a package and then
having the sole burden of updating it themselves. I also think it makes
people feel
On Fri, Aug 29, 2014 at 3:59 PM, Michael Raskin 7c6f4...@mail.ru wrote:
I would say that ZHF has some progress specifically because it is about
reasonable efforts to improve signal-to-noise.
If we want packages to get updated, we need to merge pull requests
faster and not let pull requests
Unfortunately, I don't have the exact error message anymore, but it was
related to running tests that wanted to write to /var/empty, which was
disallowed in non-chroot.
LibreOffice expression per se has no mentions of /var/empty, however.
Neither has LibreOffice source.
But it could be used by
hydraPlatforms is a reasonable solution for another problem; when the
build takes more space than time
When a build takes more space/bandwidth than time, I'd expect
preferLocalBuild = true; instead of setting hydraPlatforms.
preferLocalBuild is to save hassle for local machines;
@peti: the recent hydraPlatforms change is a hack right? Because that does
not prevent the user from trying to install the package, which will be
compiled and will fail.
hydraPlatforms is a reasonable solution for another problem; when the
build takes more space than time and the package is less
Is there any way to see full list (link at the bottom doesn't show
them)? Any way to get plain list? (so I can grep out non-linux, etc..)
Click Full list at the bottom, go to the failures tab, copy paste to
the text editor of your choice.
___
nix-dev
It's indeed a good question to ask the developers of neo4j why do they
issue this warning, especially since OpenJDK is listed as a valid JVM in
their system requirements
http://neo4j.com/docs/2.1.1/deployment-requirements/.
As Luca said you shouldn't use OracleJDK unless you have really good
It's probably not a big deal. On the other hand consider that it only
happens in a rather special scenario and may go unnoticed for quite
some time.
Consider an application (like a game) with a bunch of separate sets of
data files, each optional and referring to each other, compressed to
save
I think that any proposal would be seriously considered. Any already
existing application creating such a problem would increase your chances
to make someone else propose a solution… Otherwise — I think the problem
can surface, but I have no idea ho to fix it sanely… I think many other
people
I've actually had the same question, recently. I was planning to try a few
things myself before I ask here. But, now that the discussion is there I'll
just chime in...
Given a case where you can't get the admin to give you `/nix`, and where
you have space/compute constraints on the target, would
Another way would be to hook the path handling procedures of the libc.
Rewrite /nix/store to whatever is in the NIX_STORE variable. This
would be a lot of hard work, but would work much more reliably than
rewriting paths in binaries, and it would work without help from root.
Hmm, globally
If you guys have some knowledge that's not searchable on the web at the
moment then please do make wiki pages! It's frustrating to get stuck on
something and then asking on IRC for hours, waiting for mailing list
replies, source diving, …, knowing that *someone* already knows!
Well, not all
On 06/10/2014 02:29 AM, Daniel Bergey wrote:
A few weeks back I struggled with fonts, asked some questions on IRC,
and wrote up what I learned on the wiki:
https://nixos.org/wiki/Fonts
I should add some notes on packaging fonts there, too.
I have no idea why Cantata and chromium aren't
When we use priorities generously we could avoid a lot of delay even in
less critical cases.
The main problem I see is that normally you don't want to release a
channel until *all* parts have rebuilt.
+1 Rebuilding for a server that runs, say ssh, apache, nginx, postfix and a
few such
Calculating the transitive closure for all nixos modules / services run by
systemd is one way to prioritize. A populatiry contest could be added to
that.
Maybe having a channel which is a subset of the main channel and
includes at least ssh, apache, nginx, postgresql, mysql, and some ftp
Note that we're currently not just waiting for Hydra, but also for the
delayed appearance on the official cache.nixos.org, which AFAIK can
take something like a day.
As far as I understand, this delay is the delay of Hydra building the
entire channel. I.e. fresh Nginx will not go to the cache
too bad :-) Thanks for the find!
By the way, note that PID-1-only cgroups management is a systemd
decision, as far as I understand from the kernel mailing list posts, the
interface will still be a filesystem, and apparently it is OK to
implement cgroup management by multiple root processes
Hm, I wasn't following the kernel ml on this, but from the systemd's
document it follows that there has to be _exactly one_ writer to this
filesystem and this is a restriction forced by the kernel. systemd's
decision is that it will be PID 1, not some other process. On non-systemd
systems that can
- Help should be Documentation or Docs, I tripped over the same
thing
Actually, the design i too like GitHub where we have learned that the
top bar is about _site platform_, not about the project in question.
I don't know whether this is a problem for many others but it may be
that people
Carousels with blurbs are often annoying. You start to read and it
switches.
Just hover it with your mouse and [if it is implemented properly] it won't
switch.
I've seen carousels that keep switching if you hover them two or three times
in my life. That's braindead.
Don't know, I open a site
Hi! I am managing an nixpkgs branch and this branch become more and
more older. There already were issues where I had to change mirror
urls because of missing sources. I'd like to store as much as possible
into local repository in order to protect myself from such situations.
Is there a way to
I'm looking at the new website with mixed feelings. Being less static is a
good idea, so I appreciate the news, blog posts and commits sections. On the
other hand it's way uglier and less lucid compared to the old website.
I'm flattered you consider my shitty, amateur design from 5 years ago
nix-env -f . -i cinnamon.cinnamon-session shows the no derivations found
erorr.
nix-env -f . -iA cinnamon.cinnamon-session
?
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
For me versionDerivation looks like a nicer solution, but I generally
tend to be OK with computations written in Nix.
I have been burnt by pythonPackages and even by linuxPackages providing
different subsets of modules for different core versions… so I do not
think versionedDerivation is worse
Michael Raskin schreef op 7-4-2014 19:09:
nix-env -f . -i cinnamon.cinnamon-session shows the no derivations found
erorr.
nix-env -f . -iA cinnamon.cinnamon-session
?
Same error. It looks like Cinnamon is blocked to be found. Other
packages are not a problem.
nix-instantiate /etc/nixos
Michael Raskin schreef op 7-4-2014 19:27:
Michael Raskin schreef op 7-4-2014 19:09:
nix-env -f . -i cinnamon.cinnamon-session shows the no derivations found
erorr.
nix-env -f . -iA cinnamon.cinnamon-session
?
Same error. It looks like Cinnamon is blocked to be found. Other
packages
Michael Raskin schreef op 7-4-2014 19:17:
Hello,
I tried to use the propierty nvidia driver but I cannot make it install.
services.xserver.videoDrivers = ['nvidia'] and
hardware.opengl.videoDrivers = [ 'nvidia'] gives both a undefined error.
You need either or ''
I did
I managed to force-push master and delete a couple of commits. I have no
idea how that happened, but let's first fix the mess. Does anyone commit
nixpkgs/master 6cfbc75 Michael Raskin: Fix CL-Launch source link
If so, please force-push it to master (check before that if any new commits
I routinely find myself in a situation where some build tool or
installation of software (gcc, pip, a runtime) not via a nix expression)
will fail due to not having zlib available/in scope. What would be a simple
way to prevent this annoyance?
There are NIX_LDFLAGS, NIX_CFLAGS_COMPILE and
I've noticed that NixOS doesn't provide man pages for well-known C
functions from it's stdlib. Probably most of the users don't need
them, but I'd prefer to install it on my system. Do we have such an
option? If not, I probably can write a separate expression. What
package does contain them?
It is a trade-off. Broken packages can be more overhead than duplication
of work. If you make a package that works for you, push it to nixpkgs
and abandon it, the next person will find it broken for his purpose, fix
it and in the process break it for you. You will both spend time
debugging the
Michael Raskin 7c6f4...@mail.ru writes:
Somehow, whenever updates of packages I care about were broken, it was
a simple mistake that was easy to fix separately… I think this scenario
is overly pessimistic.
Well, depends on your point of view. If you only care about a few
packages for your
What I'm most worried about though is citrix and its critical priority to
you. But that's mostly based on my previous experiences with the linux
citrix client's hideous quality. I had a great deal of trouble just with
Arch linux the last time I used it.
If Citrix is a Java application with no
The current implementation of the 'asdf' build tool for
pkgs.lispPackages passes texlive to every package (It's used to build
documentation).
I think we should drop this input. A 500+Mb download for even the
smallest lispPackage isn't necessary.
I guess I should say that I do agree that this is
building muffin-enum-types.h
building Meta-Muffin.0.gir
GISCAN Meta-Muffin.0.gir
Couldn't find include 'Clutter-1.0.gir' (search path: […
'/nix/store/kgkd63a3q70jxmwz9p11y143xchph7y4-cinnamon-desktop-2.0.4/share/gir-1.0',
Yes, fixed. Should the absolute non free license also be added to
lib/licenses? like:
```
idea_personal = {
shortName =IDEA Personal License;
fullName = IDEA Personal License;
url =https://www.jetbrains.com/idea/buy/personal_license.html:
}
```
Instead of just unfree? I.e. do we add non
Excerpts from Michael Raskin's message of 2013-12-05 04:54:51 +:
I wonder if this is the first package I have seen with meta right
after the name in the beginning of the expression
Might be the first. I think it's better this way, as when you're
glancing at an expression, this is
And now I see this error messages:
building gnome-datetime-source.lo
CC gnome-datetime-source.lo
building libgsystem_la-gsystem-local-alloc.lo
CC libgsystem_la-gsystem-local-alloc.lo
building libgsystem_la-gsystem-file-utils.lo
CC libgsystem_la-gsystem-file-utils.lo
Anyone a clue how to solve this ?
GIO is a part of glib.
Its include path matches ${glib}/include/gio-*
I usually just expand this mask in preConfigure and add
-I$gio_include_dir to NIX_CFLAGS_COMPILE variable.
Do you use the export Nix_FLAGS_COMPILE or just NIX_FLAGS_FLAGS_COMPILE.In
Date: Sun, 1 Dec 2013 23:10:48 +0400
From: 7c6f4...@mail.ru
To: rwob...@hotmail.com; nix-dev@lists.science.uu.nl
Subject: Re: [Nix-dev] libgsystem/gsystem-file-utils.c:28:34:
fatalerror:gio/gunixinputstream.h: No such file or directory
No luck.
I changed the derivation to this ;
{
When you do not have gobject-introspection added to the buildsinput you see
this error :
./configure: line 15707: syntax error near unexpected token `1.32.0'
./configure: line 15707: `GOBJECT_INTROSPECTION_REQUIRE(1.32.0)'
builder for `/nix/store/z9mkb2m239y3fdrpxr2fhcb0j4yadki2-cjs.drv' failed
Yes, I did and I solved this problem.
Now I see this error :
No package 'gmodule-2.0' found
No package 'gthread-2.0' found
No package 'gio-2.0' found
No package 'mozjs185' found
So I did find / -name gmodule-2.0.pc and I see this output:
./configure: line 15730: `
PKG_CHECK_EXISTS(gobject-introspection-1.0,,'
builder for `/nix/store/4cr9r3lrmlvwrv8nk9x60xq88npgcm34-cjs.drv' failed with
exit code 2
PKG_ something is likely to be related to pkgconfig. Could you try
adding pkgconfig to the buildInputs please? I'd also
Not sure if this is still relevant - I'll drop my thoughts nonetheless.
I think a (web) dashboard *and* email reports would be useful. I
personally don't care very much about a RSS feed, but generating it
wouldn't be that hard either.
Email reports are mostly useful if they're
I'd like to unveil this new service, which will hopefully help us keep Nix
stuff fresh and
secure: http://vdmvtkitqc3grub6.onion.to/
This is a yesterday's scan result, it may go offline for 5-30 minutes several
times per day
as I'm working on improving it.
Do you plan to publish the scripts
I am trying to install nilfs-utils.
According to the wiki ( http://nixos.org/wiki/Install/remove_software ), I can
install a package by 'nix-env -i package for one user, or I can install it
for all users by adding it to environment.systemPackages . The second way does
not work for me for
On further reflection, I think I see how it almost might work using
derivations. Assume it is possible to have a derivation that is only
considered to be built (hand-waving part here ...) if the required filesystem
exists. Then that derivation depends on another that is only considered to be
The feature isn't used too much yet, so I suggest to comment out the
offending lines in nixpkgs/pkgs/top-level/all-packages.nix (until you
switch to upgraded version).
Thanks. That helped a bit. Now I have a problem:
error: `This version on Nixpkgs requires Nix = 1.2, please upgrade`
Is it
I want to add Riak support to NixOS. The config file is quite large and
can be complex. It also is a supported file type in my Emacs so I get
pretty syntax highlighting. Putting this inside Nix expressions losses
this feature. I think putting config files in Nix expressions is
suboptimal.
That does not give access to variables, from my understanding.
Ah yes, you are right
I want to add Riak support to NixOS. The config file is quite large and
can be complex. It also is a supported file type in my Emacs so I get
pretty syntax highlighting. Putting this inside Nix expressions
I tried to upgrade pgf/tikz in texlive to version 2.10 (which I need to work).
I succeded from a tar.gz in the debian mirror, but never from the .tdf.zip
from sourceforge. The nix expression
is not completely trivial, I managed to have an accepted [ unzip ] as
buildInputs,
but I got unzip
Hello.
It happened that running test-eval-release.sh shows some errors
but plain instantiation of eval-release.nix doesn't. Maybe --strict is
making it evaluate things that are passed through on all platforms, but
only evaluated where relevant.
I decided that this
Yes those fetchurl are my mistake and weren't used in the build anyway.
I've however made it to use_system_mpfr and removed the useless fetchs
(including the pcre source one which doesn't seem used).
To do so I had to bump the mpfr version to 3.1.2.
Patch attached. I'll be sure to setup a github
Yes those fetchurl are my mistake and weren't used in the build anyway.
I've however made it to use_system_mpfr and removed the useless fetchs
(including the pcre source one which doesn't seem used).
To do so I had to bump the mpfr version to 3.1.2.
Patch attached. I'll be sure to setup a github
601 - 700 of 920 matches
Mail list logo
