<allana>Hi guix. Python developers: when managing local development environments for Python 2 and Python 3, do you prefer using guix profiles or environments? something else?
<ngz>Hello. I have a package, retrieved with git-fetch, with a directory that is a submodule, needed at build time. I thought recursive? parameter from git-fetch would also get the subdirectory, but this isn't the case, AFAICT. What can I do? Package the subdir in another variable, add it as a native input to the main package, and copy recursively the contents of the input at the correct location in a new phase?
<ng0>is there a way to trigger user-creation? all that's missing is $HOME of the user because /home gets mounted late (this is an xfs disk, have my own mount service)
<ng0>otherwise I know I have to copy in all the skeleton
<notnotdan[m]>Hm, I am trying to write a package description. If I do `guix build <pkgname>` then it downloads some pre-built inputs and starts building the package. But if I run `guix environment <pkgname>` guix starts building the inputs from source.
<roptat>but in that case it would tell you grafting... instead of building...
<ngz>It seems that "recursive?" argument used in conjunction with git-fetch doesn't do what I think it would do, i.e., also populate subdirs from submodules.
<notnotdan[m]>rekado: sorry i am just not very familiar with the whole process. for example, in case of `guix build` it downloads the gtk+ package, whereas if i do `guix environment` it tries to build gtk+ from source
<jackhill>For better or worse, it is using autotools currently, but the autotool stuff needs to be generated before it is bootstrapped. I tried to add a phase before bootstrap in my package definition (see endpoint-management.scm), but that fails with a permissions error: "In procedure mkdir: Permission denied
<jackhill>Pointers would be appreciated. I'm not tied to using autotools if there is a better way, but I would like to understand what I've done wrong reguardless :)
<rekado>jackhill: you need to make the source directory writeable.
<rekado>jackhill: that’s a side-effect of using git-fetch.
<rekado>you can use (for-each make-file-writable (find-files ".")) or similar.
<rekado>is this going to be a tool for cluster admins to keep an overview on what users have installed?
<ngz>It seems that "recursive?" argument used in conjunction with git-fetch doesn't do what I think it would do, i.e., also populate subdirs from submodules. Am I using it wrong or misunderstanding it?
<jackhill>rekado: sort of. This is for reporting the the security office thread that I started on the mailing list a number of weeks ago.
<_tibbe>Hi! I have a problem with patching something: I defined a function in (guix build utils) and it uses mkdtemp! (guix build syscalls). But I cannot use it in a phase of a package definition because it cannot resolve mkdtemp!. Does anyone have a clue what the problem is?
<g_bor>The beignet log clearly points to a dependency like failure, that's why I did not raise it. But the ledger one is suspicious...
<g_bor>Yes, that is the row that caught my attention...
<efraim>I'm at 52% locally building armhf on aarch64
<efraim>i'll let it keep on building but i'm not expecting any problems
<g_bor>efraim: can I help somehow? Do I have anything to do regarding that? (Besides improving the web interface...)
<wednesday>Hey, so when I boot up the guixsd iso on a usb stick I end up getting a lot of "waiting for partition 31393730-3031-3031-3139-313631383738 to appear" until it gives up saying failed to resolve. The only disk in the machine should be a blank btrfs. When it fails to resolve I get slapped into a guile repl with no working keyboard, so I don't know wha
<quiliro>when showing the image of the current keyboard distribution, I get an error failed execution of gkbd-keyboard-display. command not found
<quiliro>what package am i supposed to install for this to work?
<wednesday>OK so, the reason for my keyboard not working and the partition error was the iso on the usb for some reason not liking my usb2 ports, and only letting my usb3 ports work. Is this a known thing with the ISO and will that carry over when I install(not having usb2 support)?
<apteryx>wednesday: maybe check the kernel messages under /var/log/messages for hints
<apteryx>the kernel of the liveUSB is the same as for a normal Guix system (linux-libre), so yes, it's likely you'd run into the same problem after installin.g
<wednesday>apteryx: well I see these 2 messages "usb 4-2: new full-speed USB device number 9 using ohci-pci" then "usb 4-2: device not accepting address 9, error -32", other than that it seems to be fine
<wednesday>I think I remember before on an old install of another OS I was using I think I might have had to use ehci or maybe xhci for usb 2, would you be able to do that in guixsd without having to do my own kernel?
<apteryx>wednesday: OK! Are these extra kernel modules to load (ehci/xhci)? If so, yes, I believe you should be able to do that in the operating system definition.
<wednesday>well xhci is the kernel subsystem for handling usb 3, and I believe can also deal with 2>, and ehci if another kernel subsystem for usb 2> and so is ohci, which is the one that's not working for me
<wednesday>at least that's my understanding of the whole mess of usb support
<wednesday>and also now I can see that my internet wont work, it's wired but ifconfig says something about a firmware patch being deblobbed, I swear I used a deblobbed kernel on gentoo ages ago but that might have been on another motherboard
<quiliro>what fonts are necessary to install to see all web page characters correctly on epiphany?
<wednesday>that's why I'm here heh, I don't know what I should do, I can get you my /var/log/messages so you can try see whats going on with the usb 2 if you want
<rekado>I probably won’t be of much help. I’m just thinking that building a custom kernel is only necessary if you’re missing modules or features are missing from the kernel configuration.
<wednesday>well my assumption is that they haven't built the other usb systems as modules, since xhci and ohci should be good for most people, but I don't know heh
<ngz>When I clone a repository and use git submodule update --init --recursive, git pulls data from the submodule. If I define a package with git-fetch and recursive? #t, it doesn't. I don't understand why.
<apteryx>ngz: according to the info manual, it should fetch the submodules, so maybe it is a bug.
<dongcarl>Any updates on getting guix into official repos for debian?
<rekado>ngz: does git clone --recursive work for this repository?
<jackhill>Is the best option for wrapping guile programs (so that they can find their modules) "manually" like in the haunt package?
<vagrantc>dongcarl: filesystem hierarchy standard ... e.g. directories in the top-level ... e.g. /nix or /gnu
<jackhill>I guess we don't have too many guile executables yet
<harding>vagrantc: it looks like it just uses /nix, as expected. The pacakage description links to a discussion on the debian-devel mailing list where there's general consensus for them having an exception.
<vagrantc>harding: but it creates the directories with a systemd tempfiles mechanism
<harding>vagrantc: oh, indeed. That is weird. The install script should be about to mkdir -p the required directories.
<vagrantc>harding: like i said, a curious workaround to remain FHS compliant
<wednesday>apteryx: I just gave that a go for both ohci, and ehci dirs, but either way it seems usb 2 devices dont want to work
<wednesday>well I found another thing that tells me to enable IOMMU in the bios, but that causes the usb not to boot with the same "waiting for partition to appear" error I get when I plug the liveusb in a usb 2 port, even thuogh it's in a usb3 one
<wednesday>OK another revelation, enabling IOMMU in the bios switches things about, the usb 2 ports all now work fine, but the usb 3 ports are not working, things are getting weird apteryx