Hi Andreas,
> On Mon, Feb 18, 2019 at 10:56:13PM +0100, Ricardo Wurmus wrote:
>> when installing a package into a profile Guix very helpfully tells you
>> that you may need to set certain environment variables. It doesn’t tell
>> you that these environment variables can also be set by
I'm unsure it's related. It's talking about an error while building
xxx-etc.drv. Maybe you should have a look at the actual log?
See "View build log at..."
Raghav RG Gururajan writes:
> @Clement
>
> The code didn't work. I have attached the error with this email.
> Original Message
18.02.2019, 14:44, "Tobias Geerinckx-Rice"
:
> If this is the quality of argument that ‘won’ over PureOS, it's
> blaming Guix/Ricardo for not being around to stop others from
> being bullied.
>
> Kind regards,
>
> T G-R
Hi Tobias,
I've been reading this conversation from the outside but noticed
Hello,
On Mon, Feb 18, 2019 at 10:56:13PM +0100, Ricardo Wurmus wrote:
> when installing a package into a profile Guix very helpfully tells you
> that you may need to set certain environment variables. It doesn’t tell
> you that these environment variables can also be set by source’ing the
>
Agreed.
For users using other shells, the issue is not knew.
The main recommendation I've seen (e.g. for Fish) is that the user kept a
POSIX-style shell as a login shell and only drop into the desired shell after
the profile has been loaded. This way, Guix and similar configurations
Ricardo Wurmus writes:
> Hi Guix,
>
> when installing a package into a profile Guix very helpfully tells you
> that you may need to set certain environment variables. It doesn’t tell
> you that these environment variables can also be set by source’ing the
> generated etc/profile file.
>
> I
Hi Guix,
when installing a package into a profile Guix very helpfully tells you
that you may need to set certain environment variables. It doesn’t tell
you that these environment variables can also be set by source’ing the
generated etc/profile file.
I have seen the bashrc and bash_profile
On Mon, 18 Feb 2019 11:56:19 +0200
Efraim Flashner wrote:
> I checked 'guix refresh -l python2' and I got a list of the python2-*
> packages which are leaf packages. I'm not suggesting that we right now
> get rid of them, but it seems to me something worth keeping an eye on.
>
> 'guix package
On Sun, 17 Feb 2019 10:02:26 +0100
swedebugia wrote:
> Am I late to the party?
Yes, you are :-)
We decided to split once: We now put the whole "setup and build guix
from git" part into one video. And then the real "packaging" part
starts in a second video. It might be that we need to break
"Björn Höfling" skrev: (13 februari 2019
10:13:22 CET)
>On Mon, 11 Feb 2019 11:38:21 -0300
>Laura Lazzati wrote:
>
>> Hi Guix again!
>>
>> Another topic is about showing how to package.
>>
>> Gábor suggested maybe using my experience about creating a new R
>> package.
>>
>> My idea is to
Hi Konrad,
On Mon, 18 Feb 2019 at 17:31, Konrad Hinsen wrote:
>
> Hi Ricardo,
>
> >> "My channel" doesn't exist (because I haven't yet found the time to
> >> figure out how to set up and manage a channel, although it's been on my
> >> to-do list for a while).
> >
> > I’d be happy to assist.
>
>
Efraim Flashner writes:
> I checked 'guix refresh -l python2' and I got a list of the python2-*
> packages which are leaf packages. I'm not suggesting that we right now
> get rid of them, but it seems to me something worth keeping an eye on.
>
> 'guix package -A ^python2- | wc -l' gave me 737
>
Konrad Hinsen transcribed 1.2K bytes:
> Hi Ricardo,
>
> >> "My channel" doesn't exist (because I haven't yet found the time to
> >> figure out how to set up and manage a channel, although it's been on my
> >> to-do list for a while).
> >
> > I’d be happy to assist.
>
> Thanks! I might come back
Hi Ricardo,
>> "My channel" doesn't exist (because I haven't yet found the time to
>> figure out how to set up and manage a channel, although it's been on my
>> to-do list for a while).
>
> I’d be happy to assist.
Thanks! I might come back to that offer when I find at least enough time
to figure
On Mon, 18 Feb 2019 11:53:04 +0100
Ricardo Wurmus wrote:
> Ricardo Wurmus writes:
>
> [...]
>
> The application period begins today. So far nobody has come forward
> to volunteer as a mentor, so I suppose Guix will not participate in
> the upcoming Outreachy round of internships.
Hi
Hi Chris,
On Sat, 16 Feb 2019 02:53:30 -0800
Chris Marusich wrote:
> > (i.e. the things you did before, just inside a i686-linux guix
> > environment. That only provides minimal--almost no--isolation from
> > the host, so it should allow us to test whether the personality is the
> > only
Dear,
Maybe I am wrong and I miss one point.
If you have local packages that depends on Guix packages, then it is
not a big issue when the Guix packages are removed. Because you just
have to `guix pull --commit=' where points to a Guix commit
owning the required packages.
And if I have correct,
Ah! Got it. Thank you!
Original Message
On 17 Feb 2019, 13:26, Clément Lassieur wrote:
> Raghav RG Gururajan writes:
>
>> @clement
>>
>> Thanks! Btw, shouldn't the first line be "(boot loader
>> (bootloader-configuration)" in the code snippet you sent??
>
> Well, I just gave
On Sat, 16 Feb 2019 12:16:41 +0100
Gábor Boskovits wrote:
> It seems to me, that there is a whole bunch of people interested in
> this, but due to lack of resources or for some other reasons nothing
> is really happening. Do you know any we we could help getting this
> resolved?
This is a very
bill-auger wrote:
On Sun, 17 Feb 2019 23:33:06 +0100 Ricardo wrote:
I don’t feel motivated to apologize to the people involved in
PureOS
because I wasn’t around when they were pressured / convinced to
drop
Chromium.
no, but you could have been around - you also could have argued
for
pureos
On Sun, 17 Feb 2019 23:33:06 +0100 Ricardo wrote:
> I don’t feel motivated to apologize to the people involved in PureOS
> because I wasn’t around when they were pressured / convinced to drop
> Chromium.
no, but you could have been around - you also could have argued for
pureos on their side of
Am 18.02.19 um 11:53 schrieb Ricardo Wurmus:
> The application period begins today. So far nobody has come forward
> to volunteer as a mentor, so I suppose Guix will not participate in the
> upcoming Outreachy round of internships.
Bringing KDE Plasma to guix. Considerable work has already been
Hi Konrad,
>> Konrad, going forward it might be reasonable to keep copies of required
>> Python 2 packages in your channel. We aren’t going to remove Python 2
>> packages now, but in the future we may not be able to fix unmaintained
>> packages and may have to remove them.
>
> "My channel"
Hi Alex,
[-guix-commits, +guix-devel]
>>> Again, this is the result of auto-generation: Hall generically wraps any
>>> script files in the scripts directory of a project with all Guile
>>> dependencies — rather than the developer having to manually specify
>>> these things.
>>
>> I think this
Hi Ricardo,
> Konrad, going forward it might be reasonable to keep copies of required
> Python 2 packages in your channel. We aren’t going to remove Python 2
> packages now, but in the future we may not be able to fix unmaintained
> packages and may have to remove them.
"My channel" doesn't
Hello Ricardo,
2019. febr. 18., H 11:53 dátummal Ricardo Wurmus ezt
írta:
>
> Ricardo Wurmus writes:
>
> > the next Outreachy round of internships will take place from May 2019 to
> > August 2019. As a community we would need to decide very soon whether
> > we would like to participate in the
Ricardo Wurmus writes:
> the next Outreachy round of internships will take place from May 2019 to
> August 2019. As a community we would need to decide very soon whether
> we would like to participate in the upcoming round.
>
> To make that decision we need to have people come forward who
Konrad Hinsen writes:
> Efraim Flashner writes:
>
>> I checked 'guix refresh -l python2' and I got a list of the python2-*
>> packages which are leaf packages. I'm not suggesting that we right now
>> get rid of them, but it seems to me something worth keeping an eye on.
>
> Please be careful
Efraim Flashner writes:
> I checked 'guix refresh -l python2' and I got a list of the python2-*
> packages which are leaf packages. I'm not suggesting that we right now
> get rid of them, but it seems to me something worth keeping an eye on.
Please be careful with "leaf packages". The leaves of
I checked 'guix refresh -l python2' and I got a list of the python2-*
packages which are leaf packages. I'm not suggesting that we right now
get rid of them, but it seems to me something worth keeping an eye on.
'guix package -A ^python2- | wc -l' gave me 737
the number of leaf python2 packages I
30 matches
Mail list logo
