<attila_lendvai>i'm first trying to use guix deloy, but deep into the process it dies for me consistently with ";;; [2022/12/21 21:48:56.877786, 0] [GSSH ERROR] Channel opening failure: channel 66 error (2) open failed: #<input-output: channel (closed) 7f5d2d8c9660>"
<jackhill>Kolev: we used to have it, but it's written in an unsupporeded programming language (python2) that we removed. I know there was some work on porting CHIRP to python3, but I don't think that's complete. IN the meantime, maybe guix time-machine can help you muddle through
<Guest30>Kolev: you can also take a look at the `guix-past` channel , which retains old packages that have been dropped from the mainline distribution (including python 2)
<Guest30>to be clear, the upstream there is the custom implementation `vrms-arch` , which is a rewrite in python vs the perl scripts used in debian
<Guest30>neither of which do much for mainline guix, as they either 1. check against a list of "bad" packages (in debian's case), or 2. check against a list of "bad" licenses. For guix upstream this will essentially always be empty in either case
<oriansj>well ideally yes but people do make custom channels and it should be checking those too
<Guest30>good point, in those cases it would probably be cool to have a deeper license checker (ie, crawling source code for license info)
<lechner>sneek: later tell attila_lendvai: now i have the same problem!
<guixuser>rekado I have one more question. You wrote for pine64. What command are you running it with?
<guixuser>I don't quite understand the difference for system and target parameters.
<rekado>system is for native builds; target is for cross-compilation.
<rekado>this is not my configuration, but I build my system images natively (directly on the target machine)
<guixuser>So if I'm going to create the image on a different machine, I need to use target?
<Kolev>jackhill: I thought Guix was good at supporting old software. Why not package it?
<Kolev>jackhill: The official package is a Flatpak. I guess I could use it.
<rekado>Kolev: maintaining a large number of Python 2 packages is a serious burden. We have some in the Guix Past channel.
<rekado>it’s not something we want to carry in the official Guix repo.
<oriansj>well yes Guix is very good at supporting *ALL* software; but the question about where it is packaged is more about who is responsible for maintaining it. And I do wish the various guix channels were more easy to discover; then the problem would be bob runs this channel which contains x,y,z and if you want y, you just need to include bob's channel.
<rekado>you should be able to find some “denied” messages for x-daemon or similar in /var/log/audit; and that would tell you what permissions or context transitions would need to be added to the policy
<civodul>rekado: so we ended up *cough* disabling SELinux
<pjalsDanielv[m]>hi, how do i make guix use a seperate /boot partition which is encrypted using luks1 (not efi, i use legacy boot)? i've tried to look around in the manual and found nothing. i specifically want to do this to use luks2 on / but grub doesn't like that for some reason
<apteryx>very much! and #bash has nice experts to complement it
<PotentialUser-57>Hello guys. I am running into a problem when doing guix system reconfigure, and the description is that the file used "does not return an operating system or an image". Does anyone know the reason for this to happen?
<apteryx>I think traditionally there were a bunch of 'getopt' that differed in behavior
<apteryx>but that's not much a problem nowadays on GNU/Linux systems
<PotentialUser-57>I have been also experimenting with setting up the system as modules (base config + system config that uses the base configuration) but when running guix system reconfigure I was always getting the following error: ice-9/boot-9.scm:3330:6: In procedure resolve-interface:
<PotentialUser-57>no code for module (base) Tried with sudo -E option as well, but it didn't work. My /etc/guix does not contain any configuraiton files, could that be a problem?
<nckx>PotentialUser-57: Is (operating-system …) the last form in the file? Or, alternatively, (define my-os (operating-system …)) (other) (stuff) my-os? Or, alternatively, just share your file :)
<nckx>You need to explicitly add any module load paths if you aren't doing so yet. Either with Guix's ‘-L’ CLI option, or using something like ‘(add-to-load-path (dirname (current-filename)))’ at the top of your /etc/guix/system.scm.
<nckx>I've noticed that the latter can make error messages go weird, but when it works, it works.
<rostick>The currently running system configuration is generated from the official system installer, and I use it on a secondary laptop for such experiments. My goal is to create a base configuration that can be appended for further use on my other machines and I find that the stock configuration does not serve this purpose very well, so I am looking at
<rostick>configs of other people to determine a way to do it
<msgilligan[m]>Hello, I'm trying to install and use openjdk-18 and maven with guix on Debian bullseye and I have a question...
<nckx>What do you mean by ‘meant to be overridden’? That's true for ‘guix system vm’ only.
<msgilligan[m]>... when I install firstname.lastname@example.org (or some other versions that I tried) I get a working java but I can't find a javac executable. Is there an additional step to install the javac compiler? What am I missing? Is there a place I can go for documentation specific to OpenJDK on Guix?
<rostick>nckx I didn't mean that it's supposed to be ovverriden, but rather that the "base" module is used in per-machine configurations. Although I don't quite understand how the modules work yet, so will refer to the user manual for more details
<nckx>msgilligan[m]: javac is in the :jdk output. ‘guix install [or whatever] openjdk:jdk’.
<nckx>You can list outputs with ‘guix show PACKAGE’, but there's no way (yet!) to search ‘which file/command is in which output?’. You just need to know.
<nckx>Some things are well-documented. Others are… not.
<nckx>If you want to re-use this definition you'll have to restore the define-public eventually, but as mekeor[m] suggested, making that work is as easy as adding ‘base-operating-system’, or any other valid variable, as the last line of the file passed to ‘guix system …’.
<msgilligan[m]>nckx: I guess what I would like to see (and searched for) is a "how to" on installing Java and building Java apps with Guix. I currently don't know Guix well enough to contribute to the "file search" issue. Is there a place where I could submit an OpenJDK how to?
<nckx>rostick: I shouldn't have distracted you with the ‘define’ business at this stage. It's not that important yet, only when you want to make multiple variants later.
<nckx>msgilligan[m]: Yes! You could add it to the cookbook, which is meant for targeted goals/how-tos. <https://guix.gnu.org/en/cookbook/en/guix-cookbook.html>. It's also in the Guix git repository, as a Texinfo source file (in doc/). But if you're not ready to edit Texinfo (it's just another text mark-up, nothing too scary), you can also draft a text and submit it to guix-devel at gnu dot org for review.
<nckx>elevenkb: The short answer is that it's part of GCC (gcc:lib). I don't know the long answer to ‘what's the (most) correct way to use it’, though.
<msgilligan[m]>nckx: Thanks! I'll take a look and see if I can figure out Texinfo.