<pmikkelsen>hello guix, some time ago I read it was possible to 'convert' a debian system into a guixsd one, but do you think it is possible on a VPS that runs openVZ? my understanding of it is that every VPS has to run the same kernel as the host or something :)
<pkill9>how do i untar a bz2-compressed tar file with a trivial builder?
<ng0>would've picked 1984 again, but if you're low on bugdet and have something as demanding as GuixSD the smallest instance at 1984 isn't good. you can scale up, but scaling down doesn't work the way they are made
<ng0>but if 17 - 30 euro / month is okay for you, contact 1984. they were even open to adding official GuixSD support
<ng0>I have some notes on theoretical support for IN-Berlin, but that's up to those who want to test their patience
<ng0>those ISPs differ sometmes only in minor details
<pmikkelsen>Unfortunately my budget is rather low as this is mostly for experimenting, so I think I might go with digital ocean then
<ng0>it's getting early/late here, but I'll send a short email as soon as I can
<ng0>oh. we have saturday. well, tomorrow or next weekend then
<pmikkelsen>ng0 sounds good, it's also getting late here so i better go ;)
<ng0>bsaically: follow what wingo wrote, but take the small instance/droplet (1GB RAM), upgrade it to 2GB RAM temporarily (depends on the usage but 2 GB RAM is what we still need to compile Guix without waiting for many many hours), when you come to the reconfigure step, let it fail once as written and when you do the cp+move step include "cp -r /etc/guix" in there.
<ng0>I've done this a couple of times, so I'd first experiment at home.. or use the server, you can shred it if you break it without means for recovering
<ng0>I might end up writing a script for that, but it would be tailored to my idea of the process + my wip'ish guix templating
<thomassgn>hmm, guix complains about not finding packages like python-2; both from 'guix package -i python-2' and 'guix environment python-2'. I see my $GUIX_PACKAGE_PATH only contains my own module dir. I think it used to have guix's also?
<iyzsong>thomassgn: the syntax had change to 'python@2'
<thomassgn>ok, trying. But the '.config/guix/latest/gnu/packages/python.scm' contains '(define-public python-2 python-2.7)' and a full definition of python-2.7.
<thomassgn>so it does seem to work with the @ notation, at least for guix package -i
<iyzsong>yes, packages are lookup by name@version, 'python@2' will find a package which has the name 'python' and version starts with '2'.
<iyzsong>the scheme variable name 'python-2' has nothing to do with packages lookup.
<thomassgn>ye, but if .... hmm, I clearly don't understand the mapping of that ^^
<thomassgn>but it's allright. don't have a mind to understand it now anyway :)
<shorttraveler>quick question: am i correct in believing it is only root who can create and then use arbitrary package definitions? [GUIX_PACKAGE_PATH seems ignored in non-root usage] this is something i expect to be the case for security reasons - but guix has pleasant surprises in it :)
<ngz>Hello. I'm having an error when trying to use "./pre-inst-env" (after using autoreconf -vfi and ./configure --localstatedir=/var), something like guix build error, cannot find guile.2.0.9.tar.xz for system x86_64-linux
<ngz>I didn't call "make" beforehand, would it be the reason?
<ng0>what was the decision why guix pull shouldn't support git:// URLs, or is it because of libgit2? I'M getting Network is unreachable for git:// URLs to pull from
<ngz>According to my understanding, it should be `LOCALSTATEDIR/guix/profiles/per-user/USER'
<ng0>Can someone clarify the chat some people here had about the certbot-service? If *one* certificate included multiple ALT-DNSname (name: foo.org + 2.foo.org + 3.foo.org), would this currently be an issue with the service? My only deployment of the certbot-service is a substitutes server with just one domain in the cert, but now I need more on another server.
<snape>ng0: currently it's not possible to include alt names in one certificate
<snape>that's the issue. I'm working on it. Hopefully I'll send the patches tonight, or tomorrow.
<marusich>Also, it's probably difficult because Python's site.py uses idiosyncratic heuristics to find its "site" libraries.
<marusich>As I recall the last time I looked at how it works, Python checks a few places relative to the executable path to find the libraries, so it really doesn't play well with situations in which the libraries are not installed in the same actual directory structure as the executable.
<Apteryx>I forgot the detail, I once took a look at it.
<pkill9>maybe it could be patched to look for them in a different location?
<marusich>Are you sure? Well, the last time I checked, Python went on a journey starting from its executable to find a special sentinel file (a module file, actually, which they always expected to be present), and walked the directory tree starting from the Python executable path.
<marusich>And I can't remember if they absolutized the path to the Python executable before beginning - which matters because if they do that, and if you invoke Python via a symlink tree that you have built with many libraries symlinked in from various distant parts of the file system, then Python won't find its libraries via the site mechanism.
<marusich>Anyway, I could be wrong, but somebody would need to review the code to make sure.
<marusich>I gotta run, but what's the problem, anyway?
<marusich>Apteryx, as for why we use double quotation in some places, it's probably because it's a situation where you have to pass a quoted list, which itself must contain a quoted list
<marusich>I recall being confused about that as well...
<pkill9>it can't be done though because they both will rely on PYTHONPATH var which specifies a path to the python libs including the version
<marusich>pkill9, I can understand that, but one cannot stuff everything into a single profile - there will be conflicts, either in environment variables or file paths. Why not use a second profile?
<pkill9>how would it be best to organise multiple profiles?
<marusich>It's pretty free-form. When I have created additional profiles, I've just plopped them into whatever directory is convenient. Just do "guix package -p .my-other-profile -i python3" or something in the directory where you want it.
<marusich>But yeah, not being able to install both in a single profile is particularly jarring if you are used to having both installed side by side :(
<marusich>I'm sure there are ways to fix it, but nobody has done it. In the meantime, you can use a second profile.
<pkill9>yeah, i just thought having them installed side-by-side is something suported in almost every other distribution, yet the one distro that explicitely is about being able to install multiple versions of packages together can't xD
<marusich>Then when you want to use the second profile, either you can just invoke applications directly from it, or (if you need to run Python3 and use its libraries, e.g. in the repl or for development), you'll need to run something like 'eval "$(guix package --search-paths .my-other-profile)"'
<marusich>Well...you can! But you need to use two profiles right now.