<Guest6>how is it that I can boot the installer just fine, but no installs even gets to grub? I've tried bios and uefi, manual and guided, with and without a "guix pull". Always I cannot get to the grub screen of my install.
<gnoo>Guest6: when that happened to me, it was that the bios was going the bois route and i had configured to use efi
<Guest6>gnoo: I got some errors with the guided installation. Manual seemed to work. I can get to a one-time boot screen and boot in bios or uefi, but it never even gets to grub. says something like "failed to boot"
<gnoo>if you only have one hdd(or sdd) in there that would mean grub failed to install properly. manually reinstalling grub is a pain on guix (very different than other distros)
<jackhill>Quick way to find the list of available system (e.g. to pass to the --system= option of guix-pack)?
<vivien>My v5 patch series is out! I bet not many of you have made so many mistakes in a single patch series as to require 5 revisions.
<mrwater>Now the fuser list is empty and it still says the device is in use
<bavier[m]>anyone know if a minetest update to 5.5.0 is underway already?
<mrwater>Can I force a luksClose? How do I get out of this? I understand that it's unsafe to not properly close an encrypted filesystem right?
<dcunit3d>i'm not sure. can you read the data off the partitions that you need?
<dcunit3d>what are you using fuser for? what's the typical usecase for fuser
<mrwater>Yeah, I can read it, I just can't close it because it's "in use"
<mrwater>fuser is like lsof. It says if there's processes related to a mount point working
<mrwater>It looks like I have to deactivate a logical volume situation, and none of the commands I can find on the internet to do that are available in the guix livecd
<sughosha>Hi guys and gals, could someone help me how to change GDM to SDDM in `config.scm`? By default it is loading GDM.
<mrwater>Okay, so pvcreate and lvcreate apparently used to be in the guix live image, and now they're not? How do I manipulate logical volumes?
<dcunit3d>i'm not sure how to help. the easiest way to deal would be to unmount any disks you want to save within the mapped luks device, then back them up & recreate. create a new USB image to boot from if necessary.
<dcunit3d>if you have to continue from within your current live image, then it's going to be much tougher, especially if you've started the cow store or are working off an existing system that's partially attached.
<mrwater>I can't mess with this device, it's an encrypted ssd :/
<mrwater>I just figured out that the guix package manager might work, so I can maybe install the lvm stuff
<dcunit3d>if it's a device image you can't risk losing, you always need to work from a copy of an image
<dcunit3d>they should already be on the live image afaik. it would be tough to install if they weren't
<dcunit3d>it is possible to install the LVM packages, but i'm not sure what state your system is in
<dcunit3d>did you boot from USB? is the encrypted disk a guix system?
<dcunit3d>and i'm hesitant to help you out here bc you may lose data if I'm wrong ...
<mrwater>I booted from usb. The encrypted device is a nothing system. I'm trying to make it a guix system.
<ryanprior[m]>char: you typically don't need to refer to glibc directly, what are you trying to do?
<char[m]>I'm trying to make dlopen available for cffi
<ryanprior[m]>Referring to glibc should work in general, I just verified it's defined as (define-public glibc (package ...))
<ryanprior[m]>Are you maybe doing this as part of a deferred build step where you need to import the module again?
<char[m]>ryanprior: removing base module seems to please but now it has the same complaint about libffi. unknown symbol even though it is imported
<dcunit3d>what is the best way to set up LaTeX with Guix? i'm trying to integrate emacs with Anki, but soon I'm going to want LaTeX
<dcunit3d>there are quite a few packages, but i've just been using the minimal LaTeX in emacs/org so far
<char[m]>actually, my bad. it still complains about glibc without base, I had it commented out
<char[m]>that is most strange, putting the list of packages directly in inputs instead of in a let made it happy.
<mrwater>dcunit3d: I have a hate/hate relationship with R and think that R markdown was the biggest mistake mankind ever made and that Yihui Xie should be burned at the stake for his crimes, but he *did* make a cool thing called TinyTeX, which is a minimal TeX package that can auto-pull packages as-needed using R.
<mrwater>It makes things a lot more manageable. I always use it even though it feels like I'm installing a tumor every time I do.
<dcunit3d>mrwater: lol with guix manifests, you can pluck that tumor out whenever you want.
<dcunit3d>it looks like guix has the r-tinytex package. i've just installed techlive-bin for now, but thanks for the heads up.
<zimoun>apteryx, civodul: well, I think it is time to have a “stable” branch; because I have hard time each time I run “guix pull”. Classical sysadmin do not upgrade because they fear to break without the possibility to rollback. I fear to “guix pull” because I do not know what to expect then. :-)
<zimoun>yesterday, I had a similar case with a Python package of my own. Now it fails to build.
<civodul>zimoun: i take it that you're offering to maintain a stable branch? :-)
<civodul>how did you stumble upon the autogen failure?
<cbaines>I'm guessing that the core-updates merge introduced the autogen failure, it's hard to tell though as data.guix.gnu.org is missing a load of revisions
<cbaines>given there's lots of room for improvement in general Quality Assurance processes, I think that's the first thing to try, rather than a stable branch
<zimoun>guest432145315: you need to create a file, say named channels.scm, for instance “guix describe -f channels > channels.scm”, then edit this file to set the commit your want for the extra channel. Last “guix pull -C channels.scm”. Does it make sense?
<zimoun>guest432145315: how do you identify that bla is from extra-channel and blabla from Guix ?
<guest432145315>leinad: it's a channel I don't have write access to, I can't setup branches. My use case is the following: I don't want to build the world every time I guix pull so I find a commit for which I'm sure to find my packages built by the CI
<zimoun>rekado: Ok, I am going to find this bug report and reopen thus.
<zimoun>guest432145315: “guix pull” update a local Git repo by doing under the hood “git pull”, then it checkout the mentionned commit. I miss how your proposal would work for several channels. AFAIK, extra channels are specified via a file.
<zimoun>guest432145315: 1/ it is not possible to specify the extra-channel at the CLI level and 2/ assuming it would be possible, “guix pull --commit=C1 --url=path/to/foo --commit=C2 --url=path/to/bar” so how do you know that C1 is related to foo and not related to bar?
<zimoun>guest432145315: it is not how many of the CLI parsers work. For instance, grep, -e is waiting a PATTERNS, but not -E. So ’grep -E -e 1’ is equivalent to ’grep -e 1 -E’. In the case of “guix pull”, I fail to see how it would work without rewrite this CLI parser.
<unmatched-paren>i thought that configured whether to fetch git submodules in the local directory :)
<civodul>i discover lots of funny issues while upgrading guile-3.0-latest to 3.0.8
***blacked is now known as pingpongball
<mroh>I'm trying to write a system test/marionette "test-lvm-root-os" (to fix 44877 and boot from lvm) , but can't get past `make check(-local)` (tests/graph and tests/pypi fails). Is it my version, am I doing it wrong or is this known?
<civodul>mroh: hi! i noticed that tests/graph.scm failure and wasn't sure if it was due to my changes or not
<civodul>for me "make check-system TESTS=basic" builds the system test called "basic", but that's it
<mroh>"make check-system TESTS="lvm-separate-home-os" calls "make check-TESTS check-local" for me.
<civodul>mroh: i'm confused; in Makefile.am, i have: check-system: $(GOBJECTS)
<civodul>meaning that "check-system" depends on nothing but .go files
<civodul>how can it end up building "check-local"?
<mroh>Im confused too, I also tried only executing the target there "TESTS="lvm..." ./pre-inst-env guix build -m $(top_srcdir)/etc/system-tests.scm -K" but stil it calls check-local. So I think, it's somewhere else.
<civodul>maybe you're seeing check-local in a package build, no?
<tanner40>I'm using Guix System and booted the 4th of 4 system generations. I rolled back to 3, and then reconfigured at which point I could no longer find the original 4th system generation, either in the grub menu or in `guix system list-generations`. Did it get overwritten?
<gnoo>probably. according to the manual, it'll get overwritten
<ardon>Hi, I'm dealing with this issue "ld: cannot find crti.o: No such file or directory" when running `ocamlopt`. My web searches yielded me needing to install gcc-multilib, libc-dev, and other packages which have no equivalent on guix. Any hints?
<ardon>vivien: Thanks, but I do have it installed already. I think it has to do with the fact that the OCaml compiler can target various architectures, but I'm unsure of what file would solve that issue.
<jpoiret>sneek, later tell civodul: So i've got a wip that builds now using #:autoload instead of #:use-module, but I don't know how I could test it, since a) with `make as-derivation`, you don't have (current-channels) b) the the source i'm currently using isn't git-checkoutable since it's a local checkout
<sneek>civodul, jpoiret says: So i've got a wip that builds now using #:autoload instead of #:use-module, but I don't know how I could test it, since a) with `make as-derivation`, you don't have (current-channels) b) the the source i'm currently using isn't git-checkoutable since it's a local checkout
<civodul>jpoiret: as part of "make release", we'd have to make it use $PWD as the source repo
<gordon1>does current authentication scheme allow if i for example i have a fork of guix with minor patches, to pull changes from the upstream?
<dcunit3d>from within the guix emacs package, is there a way to load a package on top of the existing GUIX_EXTRA_PROFILES loaded within the environment that emacs launches with?
<gordon1>i'm kinda stuck with that one, from my limited understanding if i have my own introduction in my guix fork i have to sign all new commits after this introduction (because .guix-authhorizations will be changed)
<gordon1>is that correct? if so that will hinder a bit convenience of forking guix even for personal use, since you have to revert to --disable-authentication
<dcunit3d>i see that I can "set the emacs environment" with (guix-set-emacs-environment &opt PROFILE)
<dcunit3d>gordon1 i don't know the answer, other than, at a minimum you should be able to stash your changes then pull and reapply the stash
<dcunit3d>i'm not sure whether you would then have to do a `guix pull` afterwards, but i think so
<gordon1>i bet i will try to authenticate changes and fail, though i didn't try it
<dcunit3d>but with guix, you can have multiple installed Guix's active (the system guix is maintained separately from the user's guix)
<gordon1>yeah, well, the issue exactly with fact that i don't want to have multiple version of guix installed, at least i don't want to have original guix installed
<dcunit3d>if you hook into that functionality, where the user's system has system, user and "custom" guix's that's probably the best way to maintain a Guix with a few patches applied (on a single system at least).
<dcunit3d>and like i said, i don't know, but i'll stay posted bc i'd like the answer
<gordon1>because it pulls pile of software i will never ever use and it will just sit in my /gnu/store as a dead weight
<gordon1>(though the task of cleaning it up looks more and more daunting with every day i spent on it)
<civodul>so, evaluation fails because of: (system-error "canonicalize-path" "~A: ~S" ("Dosiero aŭ dosierujo ne ekzistas" "aux-files/chromium/master-preferences.json") (2))
<rekado>pretty much every texlive-* package using simple-texlive-package without #:trivial? #t and a chdir phase is broken
<rekado>simple-texlive-package has a copy-files phase, which copies from the current directory
<rekado>all those packages that chdir away from the initial directory are thus incomplete
<ngz>Speaking of hacking core-updates, I have a questions about worktrees. I created one for core-updates branch, but if I modify a package, and try ./pre-inst-env guix build this-package, this just tries to build the package from master instead. Am I missing something?
<ngz>./pre-inst-env is called from the directory associated to the core-updates worktree.
<rekado>argh! “This file was generated from version 1.2beta of amstex.dtx and then underwent additional hand-editing.”
<rekado>well, this explains why the file doesn’t exist in our package…