<Gamayun>I have a package with openssl-next as native-input (requires openssl 1.1.x, which should be openssl-next). It builds ok, but when trying to run it segfaults immediately on some interaction with openssl 1.0.2. Running with '--version' also tells me that it's "Using 'OpenSSL 1.0.2p 14 Aug 2018'".
<dongcarl>Any way to disable the default sharing of PWD to inside the container for `guix environment --container`?
<mikegerwitz>dongcarl: I had submitted a patch for that probably about a year ago by now, but I haven't had time to revisit it to fix a test issue to have it committed. Until I get around to that, you can just change your directory before running the command. I have scripts that use mktemp(1) and switch to that, for example.
<leungbk>there is a haskell library and an emacs extension (and an atom extension that i'm less concerned about). currently, i've got the haskell library packaged the normal way (haskell-build-system) , and the emacs extension is taken from melpa, packaged with the emacs-build-system.
<leungbk>i think this is not ideal since both the haskell library and the emacs extension can be acquired from the same tarball. i am leaning towards using the gnu-build-system and making only a single package definition, ghc-hindent, that happens to take emacs as an input and will have the elisp library put in the appropriate place.
<efraim>i wouldn't worry about pulling in emacs as a build dependency, but haskell doesn't build on all systems currently
<efraim>I suppose if you wanted you could put the emacs extension in a separate output but I wouldn't bother, I'd just build it all in one go
<leungbk>thanks, i'll follow your suggestion then.
<g_bor[m]>I have been looking around the bug to allow services to implement a reload action. I was thinking about the issue of having the config file hardcoded on the command line. I belive it could be mitigated by providing a symlink in etc to the current config file, updating it in activation snippet, and starting the service with the symlink in the command line. This would work for most of the services having a useful reload. Do you
<swedebugia>rekado, ls: cannot access '/gnu/store/19mpkvkms7nwczivf8qlfj6c9vqbsffk-profile/lib/pkgconfig': No such file or directory
<rekado>swedebugia: what is the full output of “env” inside of the environment?
<matt`>jollyjester: have you installed your packages with a manifest file? if so, you can just copy the manifest to the new user and install with that. all the packages are already in the store so it won't rebuild etc
<matt`>if you haven't there should still be a way to determine the packages installed for user 1 and then specify to install those for user2. I think that's done by generating a manifest, but i would have to look into it
<rekado>jollyjester: provided by ncurses. Or you could just type Ctrl-L.
<swedebugia>rekado, the invokation pkg-config-path is wrong. Does not exist. running CONFIG_SHELL=/bin/sh /bin/sh ./configure --localstatedir=/var PKG_CONFIG_PATH=/gnu/store/19mpkvkms7nwczivf8qlfj6c9vqbsffk-profile/lib/pkgconfig --no-create --no-recursion
<rekado>swedebugia: one thing that’s weird: it references two environments
<rekado>this is one profile: /gnu/store/y460czfhah18pwvba8d2q6rd11czkn03-profile; and this is another: /gnu/store/wqrvr5b7gq8sxsj4sh4yaqlji5dmy724-profile
<rekado>it may be a good idea to look into your shell init files ~/.bashrc and ~/.bash_profile (if you’re using Bash)
<swedebugia>aha can this be because of fsad? I have that in my bashrc.
<swedebugia>I guess the error is in there somewhere, yes. Thanks for help debugging.
<swedebugia>rekado, ok. Maybe this being so an essential way for guix to work we should have some sort of troubleshooting section in the manual? I have used gnu and bash for years without, it seems, to understand how environment variables work behind the scenes.
<Tirifto>quiliro: Mi scias; saslibre ĵus demandis, kiel vi fartas, sed vi responde demandis al mi. Tial mi responde demandis al saslibre, por ke niaj demandoj pri fartoj faru triangulon. :P
<Tirifto>quiliro: Jes; je la sekva monato. Mi okupiĝas pri aliaj aferoj ĉi tiun monaton. Mi planis mian agadon al monatoj. La sekvan mi volas ankaŭ esplori Sĥemon, kaj precipe Guile-on, Haunt-on, kaj Skribilon.
<hulten>About the "/var/run/shepherd/socket: Permission denied", I forgot to mention that I am using Guix System, upgraded last night.
<hulten>(GuixSD is now called Guix System, right?)
<matt`>how can i get cow-store-service-type into my own custom config? since the provided usb installation image isn't working for me I'm configuring my own but having trouble getting the cow-store to be an available service
<matt`>i tried (use-modules (gnu system install)) but it's not working for me
<str1ngs>matt`: are you installing from a foreign distro?
<str1ngs>cow store is only required due to limitation of ramfs on the usb installer
<str1ngs>your usb is a full guix system. so /gnu/store will remain populated anyways
<anon321anon123>Hello everyone! How well wayland supported right now? I am interested especially in sway
<matt`>oh ok great. so skip that, go straight to guix system init and then boot directly from there?
<str1ngs>matt`: right, in fact because you are replacing arch. I not using cow store means the USB's /gnu/store will be persistent. so that if you have problems booting the new OS. you wont need to re download substitutes. and you can recover and init faster
<bandali>i’ve definitely seen it in parabola (based on arch), but not sure if guix has it too?
<str1ngs>I guess with emacs-git file names could conflict with emacs should you use both packages
<str1ngs>most autotools you can change the bin names though. but I think replace would work better?
<bandali>hmm i’m not sure? i hadn’t thought of that so far
<xavierm02_>My network-manager doesn't autoconnect to the network. Anyone has this problem?
<nullsix>hello guix, another day nckx helped me put startx to work with special-files. But the common user cant run the special file, indicating lack of permissions. "parse_vt_settings: Cannot open /dev/tty0 (Permission denied)"
<emacsomancer>vagrantc: I got it to build locally last time. but this time is gets to some part and locks my computer (while still overheating; until I Alt-PrtSc+f at which point it immediately shuts down due to overheating)
<emacsomancer>is there a guide to how to build a package on a different machine?
<rubic88>emacsomancer: I'm re-attempting ungoogled-chromium again after upgrading my X220 to 16GB of ram. Install has been > 2h25m so far.
<Marlin[m]>ungoogled chromium builds just fine on my main machine
<swedebugia>I really dislike the dev experience I have with Guix. Today I compile from scratch (1h wait) prepared a patch for guix.info in a separate branch, switched back to the master branch and now I have to compile everything again for some reason because of a ABI breakage with the zip bindings. Now I wanted to work on grin but it is untestable as long as git messes the go-files up all the time.