Hi!
Ricardo Wurmus skribis:
>> Can we aim for a v1.0 release? At least for the package manager? I am
>> facing people that say Guix is not mature and therefore insecure and
>> therefore they can justifiably ignore my pleas for installation
>> without even looking.
>
> I would like to leave 1.0 f
Hello!
The plan looks good to me!
Ricardo Wurmus skribis:
> * breakage since the last core-updates merge. Since the long overdue
> merge of the “core-updates” branch we have a few serious problems on
> i686 (e.g. the gst-plugins-base package) and armhf. Who would like to
> lead an effor
On 2018-06-14 17:01, Ricardo Wurmus wrote:
Oleg Pykhalov writes:
Would any of you like to document this in the manual?
I would because I posted articles like the current one sometime ago.
Excellent!
Maybe a separate ‘users-stories.texi’ should be as was discussed
somewhere on a mailing
Hi Ludo,
> The plan looks good to me!
>
> Ricardo Wurmus skribis:
>
>> * breakage since the last core-updates merge. Since the long overdue
>> merge of the “core-updates” branch we have a few serious problems on
>> i686 (e.g. the gst-plugins-base package) and armhf. Who would like to
>>
Hello,
Thorsten Wilms skribis:
> You can interact with the daemon:
>
> cd /path/to/guix/root
> sudo mount --bind /dev dev
> sudo mount --bind /proc proc
> sudo mount --bind /sys sys
> sudo unshare -m sudo chroot . /run/current-system/profile/bin/bash
> source /etc/profile
>
> guix-
On 15.06.2018 17:01, Ludovic Courtès wrote:
I haven’t tried, but something that would be equivalent to booting into
the system is:
chroot /path/to/guixsd
/gnu/store/*-guile-2.0.3/bin/guile /run/current-system/boot
It may interfere badly with the running system (like when it tries to
bring
Hi Marius,
> Now that 'core-updates' is merged, it's time to get 'staging' rolling
> again. We have lots of minor updates this round, mostly on the
> graphical side. Is there anything we're missing that's eligible (<1200
> rebuilds)?
The ant-build-system needs to be modified to raise an excep
Hi Ricardo,
I have fixed the errors mentioned bellow, Please do check and notify me
for further modifications.
>>> The next steps are to fix the errors in the regular expressions that
>>> swallow certain space characters and to re-read the documentation of
>>> “make-soft-port” to make sure that th
Hi Sahithi,
> I have fixed the errors mentioned bellow, Please do check and notify me
> for further modifications.
Excellent, this looks better. Unfortunately, your patch includes a
couple of unrelated indentation changes. Please remove those.
Let’s talk about the next steps.
1) Enabling c
