On Tue 27 Jun 2017 19:43, Mark H Weaver writes:
> Andy Wingo writes:
>
>> On Wed 21 Jun 2017 09:55, Roel Janssen writes:
>>
>>> For a long time now, I have a tearing issue on GuixSD (parts of the
>>> screen do not get updated while others do, resulting in dissapearing
>>> text in Emacs).
>>
>>
Hello. I recently learned about GuixSD, and it seems like a distro
I would actually _enjoy_ using. Essentially, my questions are:
What is the current state of GuixSD? Is it currently too buggy or
feature-deficient to use as a day-to-day os?
How can I best contribute?
-Andrew
Hi and welcome,
On Tue, 27 Jun 2017 18:16:08 -0400
cinde...@hushmail.com wrote:
> What is the current state of GuixSD? Is it currently too buggy or
> feature-deficient to use as a day-to-day os?
I'm using it every day, also for professional programming.
It's quite okay to use. There are occass
Hi Cinder,
Welcome to Guix!
cinde...@hushmail.com writes:
> Hello. I recently learned about GuixSD, and it seems like a distro
> I would actually _enjoy_ using. Essentially, my questions are:
>
> What is the current state of GuixSD? Is it currently too buggy or
> feature-deficient to use as a da
On Wed, Jun 28, 2017 at 03:49:43PM +0200, Danny Milosavljevic wrote:
> Note that a normal GuixSD system takes at least 80 GB of disk space
> (it will suck), better 160 GB (that will work very nicely). That
> mostly because of the rollback feature.
This seems very high to me. I had >100 system gen
cinde...@hushmail.com writes:
> Hello. I recently learned about GuixSD, and it seems like a distro
> I would actually _enjoy_ using. Essentially, my questions are:
>
> What is the current state of GuixSD? Is it currently too buggy or
> feature-deficient to use as a day-to-day os?
>
I use it on my
Andy Wingo writes:
> On Tue 27 Jun 2017 19:43, Mark H Weaver writes:
>
>> In the meantime, how would you feel about pushing the following commit
>> to master? It would still allow the use of SNA by explicitly asking for
>> it in xorg.conf, but auto-configuration would choose UXA by default.
>>
It was hinted at ~1 week ago in the public "Stack Clash" discussion on
oss-security, but now there has been an announcement: the private
linux-distros early-notice security discussion and coordination mailing
list is accepting new members:
http://seclists.org/oss-sec/2017/q2/638
The criteria are
Leo Famulari transcribed 14K bytes:
> It was hinted at ~1 week ago in the public "Stack Clash" discussion on
> oss-security, but now there has been an announcement: the private
> linux-distros early-notice security discussion and coordination mailing
> list is accepting new members:
>
> http://sec
Now I have found that 'guix pull' is too slow,
I need 3 hours to compile guix, is it possible to speed it ?
--
I'm also trying to understand the cause of this.
I still don't have enough time to begin investigating it or to suggest
improvements, but I notice that it gets worse and with *more* resource
usage if you pass the `--cores`/`-c` option with any value to `guix
pull`. Without this option the resource
On Thu, Jun 29, 2017 at 06:58:28AM +0800, Feng Shu wrote:
>
> Now I have found that 'guix pull' is too slow,
> I need 3 hours to compile guix, is it possible to speed it ?
Wow, that's really slow :(
I don't know of any easy way to speed it up. Maybe you could build Guix
on a faster computer and
Hello,
Currently compiling './pre-inst-env guix build --target=i586-pc-gnu
bootstrap-tarballs' on core-updates fails with:
--
phase `set-paths' succeeded after 0.0 seconds
starting phase `install-locale'
warning: failed to install 'en_US.utf8' locale: Invalid argument
phase `install-locale' su
"Feng Shu" writes:
> Now I have found that 'guix pull' is too slow,
> I need 3 hours to compile guix, is it possible to speed it ?
Maybe you can try building from git instead? I used to run
'$ guix pull && guix package --upgrade', but it gets slower as the
number of packages of guix increases. S
Hello everyone. It's already almost July! Which means I've been working
on replacing the build daemon for about a month now. So it seems like a
good time for an update.
So far, I've replaced the register-path procedure in store.scm, which
means we now have some support for using sqlite (via guile-
Leo Famulari writes:
[...]
> But, the "Stack Clash" issues took us by surprise and we spent a few
> days writing and testing our fixes. We are committed to supporting
> 32-bit platforms where these bugs are apparently easy to exploit.
> Without access to the exploits or detailed discussion, it wa
16 matches
Mail list logo
