IRC channel logs


back to list of logs

<leoprikler>once from tty, once from ssh
<leoprikler>same result in both
<guixy>I have stuff running so I'm not particularly willing to check...
<leoprikler>you don't have to; I'll consider writing a bug report if it happens again
<raghavgururajan>lle-bout: Yay! Thank you!
<raghavgururajan>> * rekado uses icecat
<raghavgururajan>rekado: How to you manage to browse GitLab?
<guixy>I am not familiar with how Debian's package manager works, but it looks like they configure w3m with "----enable-image=x11,fb+s"
<guixy>I don't see that in the guix w3m
<ryanprior>Debian defines packages using directories that have build scripts and config files. Those ought to be a rich source of ideas for how we might build our packages.
<leoprikler>`guix pack --format=deb` when?
<genr8_>I suggest gentoo as well
<leoprikler>Gentoo and Arch are nice patch sources :)
<apteryx>leoprikler: I've heard this before
<apteryx>there may already be a bug report for it, not sure
<apteryx>raghavgururajan: well done for the mediastreamer2 test suite!
<raghavgururajan>apteryx: :-)
<apteryx>do you remember what the (("O_BINARY") "L_INCR")))) substitution is for?
<raghavgururajan>apteryx: There was a name-space mistatch while enabling portaudio ot pcap.
<raghavgururajan>Regarding tester-->test, the latter represents both test-executable and test-data for the output. :)
<raghavgururajan>Also will be consistent with other generic output names: doc debug test ...
<apteryx>I like to think of the output name matching what it *is*; it's doc, it's debug (symbols), it's a tester
<apteryx>bikeshedding territory ;-)
<apteryx>if we had many packages installing test material of many kinds I would agree though. But this tester thing is very Belladone specific
<apteryx>bcg729 is in
<cdegroot_>Something wrong in the docs? has a quoted name, but I only got it to work by dropping the quote.
<apteryx>I think the quote in the manual are not single quotes
<apteryx>I'm not sure, but copy pasting things have caused issues before, because the printed character differed to what I expected it was
<apteryx>but in this case it seems to be fine
<apteryx>the name is a symbol; what failed? do you still have the error and the original version?
<apteryx>raghavgururajan: when we're done we'll have to update to 4.4.35 ;-)
<apteryx>it's probably a painless bump, I'll try it before it's tested ready to merge
<cdegroot_>The quote in the manual seems to be an actual quote. I couldn't get it to work - got scheme stack traces when I depended on nonguix as "(name 'nonguix)", tried various things, then "(name nonguix)" worked. Doesn't make sense.
<cdegroot_>(I didn't copy from the manual but from my channels.scm)
<raghavgururajan>true about the territory. xD It was short and crisp. anyway.
<raghavgururajan>You mean new version released during this timr?
<raghavgururajan> /me check back logs
<raghavgururajan>.me already took double-dose of zopiclone
<jackhill>cdegroot_, apteryx: it's a bug in the manual that was fixed, but I guess hasn't made it to the web version yet?
<jackhill>there may have been some problem building the devel version of the web manual, but I wasn't paying as much attention then :)
<jackhill>for why it's different in the channel dependencies v. channels.scm the former is data and the later is executable scheme code as I understand it.
<cdegroot_>thanks for confirming I'm not crazy :-)
<lle-bout>raghavgururajan: see builds for core-updates related to our merge here:
<lle-bout>raghavgururajan: more informative URL:
<apteryx>jackhill: perhaps because of the guile-lib update that I made.
*apteryx checks guix-devel
<apteryx>doesn't seem to be anything about that
<apteryx>raghavgururajan: was there a reason you added python to belle-sip? I seem to get away without.
<apteryx>also, it builds fine without antlr and java; can we drop those?
<brendyyn>pkill9: the removal of qt-4 broke your packages-free channel D:
<brendyyn>I was wondering how do I specify a local git repo in as a channel url?
***sneek_ is now known as sneek
<brendyyn>Got it. I needed file:/// with 3 /'s
*i1l just seen
<rekado_>raghavgururajan: I don’t browse Gitlab.
<rekado_>raghavgururajan: but I hear that switch the user agent string might be enough.
<tissevert>hi Guix !
<tissevert>wow the flow of mail on guix-devel and guix-patch is impressive Oo
<brendyyn>tissevert: more more more! we should thank all reviewers
<tissevert>but I'm amazed how interesting all of the mail is : unpiling what got in since I signed up yesterday evening and I've already learnt at least 3 helpful things if I'm to ever submit any package
<tissevert>so yeah, thank you @reviewers for all the amazing work
<nixo_>zimon: I'll have a look at your julia patches again soon, I got stuck building julia 1.6, which build fine and work fine but there are a few failing tests .-. and running the test suite requires something like 6 hours
<nefix>Good morning! Is there a reason why Guix's Go package is at version 1.14 and not at 1.16? Is it just that no one has updated it yet? If so, how should I try to update it? Thanks!
<nefix>Also, I have a local package that I'd like to contribute to the main repos, how should I do it? Thank you :)
<brendyyn>nefix: i suspect it's just work to be done. 300 packages depend on go so it would involve testing all of them.
<yoctocell>nefix: See the contributing guide in the manual:
<brendyyn>nefix: to contribute to guix you need to install it and then clone the guix repo to build locally and edit. have you done that?
<brendyyn>nefix: do you need to make use of go 1.16, or do you want everything in guix to be using 1.16?
<nefix>brendyyn: I need to make use of Go 1.16. It introduces a important package to stdlib and lots of libraries are starting using it
<nefix>brendyyn: no, I haven't edited the repo, I didn't know where to start. I have my own little repo with some configs and packages, but the whole Guix repo it's a bit scary xD
<nefix>Thanks for the link, I'll check it out
<brendyyn>nef you could also do it in your own repo i guess
<brendyyn>nefix: in gnu/packages/golang.scm there is the line define-public go-1.14. That's what you want to use as a basis for defining go-1.16. Most likely it will require changes to work
<nefix>brendyyn: I could inherit it in a local package, couldn't I?
<nefix>And then make the required changes
<nefix>Ok, I'll try it out
<nefix>I'll see the changes in nixpkgs, it's really useful to see how they do things and then adapt it to Guix xD
<nefix>And if it works out, I'll try to contribute it
<brendyyn>i suspect things will break, so i'd then just copy paste the entire go-1.14 definition and start editing it
<lle-bout>hello! :-D
<lle-bout>cbaines: I see builds done here: - but quite slow since it's been since yesterday and only 3 packages have been built
<lle-bout>civodul: watching your talk related to guix-explorer
*lle-bout needs to watch all other talks about GNU Guix in FOSDEM 2021
<cbaines>lle-bout, I think there was a backlog of package sources to build, but I think core-updates stuff is now at the top of the queue
<lle-bout>ungoogled-chromium's Picture-in-Picture mode is really nice in that I can pin a video to a corner of my screen and it moves in all my XFCE workspaces when I switch so it's just always there, so nice!
<lle-bout>cbaines: I see okay! Thank you!
<valerii_leontiev>Is it any way to add different versions of nodejs to repo?
<lle-bout>valerii_leontiev: creating packages for nodejs is a time-consuming process and no one has done so yet, so it's possible but no one could put the energy for now.
<valerii_leontiev>Got it. It's sad.
<lle-bout>valerii_leontiev: please try contributing if you need that!
<lle-bout>then it will be happier for everyone!
<lle-bout>valerii_leontiev: there's an initiative here: - reach to the participants
<lle-bout>testing work and feedback is also useful
<lle-bout>civodul: I strongly welcome addition of guix-explorer to GNU Guix itself, I find it very very useful to understand what's going on!
<nckx>Morning, people of Guix.
<lle-bout>nckx: morning!!
<lle-bout>If people didnt see it, this is wonderful!
<nckx>Oh, is that still supposed to work?
*nckx tries!
<nckx>lle-bout: How did you run it, and how long did it take to start?
<lle-bout>nckx: see - for why I can't run it on my config now
<nckx>I vaguely remember #f featuring prominently in my stacktrace.
<nckx>It also takes minutes to start.
<nckx>Both are fine, I don't expect OOTB magic from cool quick hacks.
<nckx>(It's still compiling things(?), so 5 mins so far.)
<nefix>So, compiling Go 1.16 is throwing the following error: 'ld: cannot find crt1.o: No such file or directory'. It's failing a test that says 'Test that we can use the external linker with a host syso file that is embedded in a package, that is referenced by a Go assembly function.'. Does anybody have a clue?
<nckx>Ad inf.
<nefix>It seems to compile 1.15.10 correctly though :think:
<i1l>lle-bout: hi Guix. i remember Nix mirrors things from some repos, like ELPA or so (acc. to the manual). I mean, may Guix mirror the nodejs, in place of repro-builds, in a meantime? To make Node a tging in Fuix i mean.
<i1l>heh, a virtual keyboard.
<nefix>So, continuing with the 1.16 compilation, the file that is breaking is this one: it doesn't exist in the 1.15 version, so that's why it's compiling correctly :)
<nckx>i1l: What's wrong with the current hosting?
<nckx>nefix: Heh :)
<nefix>Oh, I didn't look correctly
<nefix>It does exisist in 1.15
<nefix>Let's see what changed
<i1l>nckx: i heard nodejs is not a thing in Guix yet. thought maybe "snapshotting" node can make it reasonably pseudoreproductive.
<nckx>Yeah, it's a nightmare to build npm packages from source, since they're not intended to be.
<pkill9>npm is evil
<nckx>Well, yes, that aside :)
<pkill9>npm was created by some spiteful greek god
<nckx>Loki isn't Greek.
<pkill9>maybe it's prometheus' revenge for humans getting the power of fire
<i1l>pkill9: as someone said "evil is killer, for example. it is wrong word to describe a tech".
<nefix>So, the only relevant changes that they've made is the test skip conditions: '[!exec:cc] skip' -> '[!cgo] skip'
<nckx>Well, fire is one solution to npm.
<i1l>buttfire grenadiers of regiment going to crusade the Node. (Breaking)
<i1l>i think it is a thin red line thing. i am deserting from the regimen...
<nckx>i1l: Nix mirrors things like ELPA because they like to change what a given URL returns over time (unversioned tarballs). That's not the issue with npm, so not a solution.
<nckx>‘they’ = elpa.
<nckx>I mean, I wish it were that simple.
<nefix>Soooo I think is that is beacause it's missing the '-r <gcc-lib>/lib' ldflag in the test...
<nefix>How could I edit a file from the source using an inherit package?
<nefix>I'm seeing a lot of (substitute*) functions, but I'm afraid of replacing the whole phase and not just "appending" to the already existing substitutions
<nckx>nefix: Add a new phase before or after it if you don't yet want to touch the package you're inheriting from (which sounds sane).
*nckx AFK.
<nefix>nckx: thanks! Makes a lot of sense!
<lle-bout>pkill9: speaking of gemini clients:
<pkill9>oh sweet, I like lagrange
<pkill9>i've been running the appimage currently
<pkill9>what's the-foundation?
<pkill9>oh nvm
<pkill9>it says right the in the package definition
<lle-bout>nckx: I don't think npm packages werent made to be built from source, more so that semver compliance isnt the most strict there, that there's lots of micro-dependencies meaning multiplication of packages, also package-writing practices and maintenance quality of them are some times rather poor because lack of clear guidelines and good tools in the community.
<lle-bout>It's a result of the individualist packaging philosophy
<lle-bout>Without community and collective maintenance of packages
<lle-bout>pkill9: the package definitions I posted in the issue just works so if you want to use it feel free
<lle-bout>Pending I submit it to GNU Guix proper
<lle-bout>pkill9: see
<civodul>lle-bout: hi! just replied here:
<civodul>lemme know how it goes
<lle-bout>civodul: I have my channels defined in /etc/guix/channels.scm - but investigating
<lle-bout>thanks for answering
<nckx>lle-bout: <I don't think npm packages werent made to be built from source> Then think again, or try to bootstrap any and despair.
<rhou[m]>Do I have to run `pre-inst-env` inside the guix environment?
<nckx>rhou[m]: It's recommended.
<rhou[m]><nckx "rhou: It's recommended."> I always get `guix build: error: failed to connect to '/usr/local/var/guix/daemon-socket/socket': Connection refused`
<nckx>I'm not much help debugging non-Guix Systems.
<rhou[m]>I'm on ubuntu 18.04 btw
<nckx>Did you omit --localstatedir=/var deliberately when building Guix?
<nckx>It might be harmless, but only if all of your Guix installation follows suit.
<davidl>I have a package from centos that I can install with guix with some hassle of first manually downloading the package and unpacking and repacking it and moving patches in place. I need some help to replace the unpack step of the gnu-build-system. How do you do that correctly? I did with a modify-phases thing and a lambda, but when running guix build -f mypackage.scm Im still getting an error from tar
<davidl>xvf that it's not a tar archive.
<nckx>davidl: Paste your package to Debian's bin.
<rhou[m]><nckx "Did you omit --localstatedir=/va"> I just ran `./configure` and `make` did I need to set `--localstatedir=/var`?
<davidl>nckx: the system command there should be removed, but the main point is that the unpack phase do not seem to actually be replaced.
<i1l>davidl: try add (display "hello-Replaced unpack") to the new 'unpack to know for sure.
<brendyyn>anyone know how to make nix installed applications use fonts installed via guix? (on guixsd)
<nckx>rhou[m]: Guix should work it without it, but I don't know if it's well-tested. Does that socket file exist?
<nckx>davidl: That's not the error I get:
<nckx>i1l: It runs.
<lle-bout>nckx: I already built npm packages and bootstrapped from source, I think there's bigger problems in other areas of software. The problem is not that they were designed to not build from source (as if it were intentional), but that there has not been an active community of people checking this property and actually bringing the issues to the upstreams.
<davidl>nckx: weird.. I get this
<lle-bout>What I disagree with is that they would somehow be designed to not build from source, which to me isnt true
<nckx>I never said they were designed to not build from source, lle-bout.
<nckx>Nobody's saying that.
<nckx>davidl: OK, I see what's going on.
<lle-bout>nckx: you said they werent intended to be, they are, otherwise the source wouldnt even be released, it's just often they are only half-way into that process because it's extra effort some developers can't afford vs making the thing work for users.
<nckx>I'm not interested.
<nckx>I had to comment out all your patches in order to build the package, because I don't have them. So I'm getting the error from the unpack phase, but you're getting it from patch-and-repack, since you're asking Guix to apply your patches to an .rpm file and it doesn't know how to (it tries to treat it like a tarball).
<davidl>nckx: ah, great, thanks!
<nckx>I wonder what the least ugly way forward is... :)
<davidl>yeah, I couldn't find a good version of that package anywhere else. The patches come with the rpm so perhaps modify phases to just apply those, instead of storing them separately in Guix.
<davidl>I managed to set it up with email-passwords and TLSv1.2 on Guix, so I thought it would be nice to add this version of the package to Guix master.
<nckx>Something like that, but then you'll have to deal with the ugliness of getting them to the ‘build side’ yourself. It's not that hard, but it's something that (patches ...) magically does for you otherwise.
<nckx>davidl: If it's all buildable from source, go ahead!
*nckx AFK.
<nckx>(Last day all shops are open, here...)
<davidl>nckx: I will struggle doing it that way. The easiest way would be to upload a tarball git my own git repo and add the patches separately to Guix.
<cdegroot_>Is there some secret magic around channels I am missing? I've setup a channel, added a dependency I need, added a package, popped my pgp key on the correct branch, etcetera. Adding it to channels.scm gets it pulled but then trying to build the derivation I get an error, the log just says "(exception unbound-variable (value #f) (value "Unbound variable: ~S") (value (channel)) (value #f))". I've verified my setup a bunch of times (
<cdegroot_>1191211/) but can't find anything obviously wrong. The single recipe in the channel works if I feed it to "guix build"...
<soouul>i am back once more with more stupidity
<soouul>whats the proper way to set up global environment variables?
<lle-bout>soouul: hello! I don't see stupidity! Actually it's not clear to me how we can do this, that is, add global environment variables. Depending on where you want them to apply, you could export them in your .bash_profile or else, as this source is sourced at login.
<soouul>where its for qt5ct
<soouul>and usually i would just add it to /etc/environment
<lle-bout>soouul: so it's about your own usage after login? not for the whole system?
<soouul>sure, i dont think i actually care if its system wide
<lle-bout>If so, use $HOME/.bash_profile (or else depending on your shell)
<soouul>i dont share my pc with anyone >:(
<soouul>lemme try on zsh
<soouul>thats what i use
<lle-bout>.zsh_profile then maybe
<lle-bout>.profile may also work but for me with bash it does not
<soouul>lemme try, i never use .profile
<soouul>its ~/.profile right?
<lle-bout>soouul: yes
<nckx>soouul: Use (simple-service 'my-global-env session-environment-service-type '(("HERP" . "blerp") ...))
<soouul>does that have to go inside another expression or alone?
<nckx>In your (services ...) field.
<soouul>you know, i was already making a ~/.profile file lmao
<nckx>That's fine, but it's not global.
<soouul>not used to this whole declarative thing, and also making a package seems easier than working around make install
<lle-bout>Thanks nckx
<nckx>lle-bout: It's normal you didn't know about it, it's not documented...‌ :-/
<nckx>Not a hint, but feel free to take it that way 😉
<soouul>on the "..." you put, i can add more variables right? :O
<lle-bout>nckx: I don't feel at ease with texinfo or knowledgeable enough about GNU Guix to write good GNU Guix docs
<nckx>soouul: Yep.
<lle-bout>nckx: I would rather write notes in a collaborative draft anyone can search and edit without version control or approval process
<nckx>lle-bout: Fair enough.
<lle-bout>This way, there's no way I can be wrong because no one expects it to be, and information is still readily available, in a less formal way, but still available
<lle-bout>Things could be selectively picked in the official manual but that would make a good staging area
<lle-bout>Maintaining commit history is tedious and often I am not ready to put that effort and I'd rather be able to do things without doing it else I wouldnt do them at all (happens a lot now)
<nckx>You can use the w-word here. You won't be banned for saying wiki. Nor for creating your own if you like.
<lle-bout>I would really like if we had a!
<lle-bout>Libreplanet looks good but I don't feel like we can have the freedom we want there
<lle-bout>Also the wiki would have to be publicized on the main GNU Guix page and being under makes more sense I think
<lle-bout>Also there's the question of whether we make it an official resource or unofficial resource so that people can also talk about nonfree things when they remain needed
<lle-bout>I think in some way both must exist
<nckx>I don't think there's interest in an official wiki. Too much work; wikis attract nonsense (see: any distro wiki), and keeping them sane takes a lot of work *on top* of writing submissions, and until then the submissions just sit there under being wrong.
<lle-bout>It's no big deal if they are wrong
<lle-bout>It's better than if there's nothing
<lle-bout>Many GNU Guix package definitions are wrong
<nckx>I can't agree.
<lle-bout>Then we wont have a wiki and information will not flow through users, *shrugs*
<nckx>lle-bout: Have you tried Guix's ikiwiki package at all, perchance?
<lle-bout>nckx: nope
<nckx>It's... very old, especially for a Web Thing.
<nckx>Although it's static so meh.
<soouul>sorry to intrude again but this is not working :(
<lle-bout>soouul: did you reboot?
<soouul>no like, it doesnt let me reconfigure
<lle-bout>soouul: oh what's the error?
<soouul>invalid field specifier
<soouul>and shows the whole service expression
<lle-bout>soouul: ah yes, well you need a list
<lle-bout>soouul: append it after openssh-service-type, not above
<soouul>thenks it worked lmao
<soouul>well imma reboot and report on how it went
<lle-bout>soouul: great! alright!
<rekado_>there’s really nothing wrong with using the Libreplanet wiki for WIP progress snapshots. It won’t ever be official documentation and if anyone asked me I’d vote against ever elevating a wiki to ‘official’ status.
<rekado_>it really doesn’t need to have a home on the domain, which is where we take responsibility for content
<lle-bout>rekado_: I have a feeling that if things are not official people don't use them though.
<ennoausberlin>Hello. I try to create a package definition for python-asttokens but it fails with python-six unbound variable. What might be wrong?
<lle-bout>ennoausberlin: did you bring (gnu packages python-xyz) into scope?
<lle-bout>ennoausberlin: also share your package definition
<soouul>it did work!
<lle-bout>soouul: yay!
<soouul>thanks to both of you!!
<lle-bout>rekado_: I think the secret to good community resource is that knowledge about it must be very widespread (link on official GNU Guix website) and that there must be next to zero gate-keeping before edits are live.
<nckx>lle-bout: Well, yes, but that's because of what ‘official’ connotes to them: reliable, approved, curated. The former without the latter is (IMO!) meaningless bait-and-switch.
<guixy>Hi guix
<guixy>From gparted, navigate to broken device. device-> Attempt Data Rescue... "This feature uses gpart. Please install gpart and try again."
<guixy>Is gpart included in any package?
<ennoausberlin>le-bout: Do I need python-xyz? I will try
<lle-bout>nckx: I think it's more because it's not as widely know if it's not official, minority of people know about the resource.
<nckx>guixy: I don't think so...
<nckx>This one?
<guixy>nckx, I think so
<nefix>I've successfully compiled Go 1.16 :D
<nckx>guixy: Not packaged yet.
<lle-bout>nefix: yay!
*nckx has to run.
<nckx>nefix: Congratulations!
<lle-bout>guixy: there's also ddrescue package if that's interesting to you
<nefix>For the contribution, should I change the default to 1.16 or leave it at 1.14?
***jonsger1 is now known as jonsger
<ennoausberlin>le-bout: Now I get one line further and it fails for unbound variable python-pytest
<lle-bout>nefix: two steps separate, first submit, then discuss to change default, also changing default means lots of rebuilds so.. I already upgraded go on master for security reeasons with lots of rebuilds and it went fine though, as long as it doesnt break stuff I think it's OK to change the default
<brendyyn>nefix: to start with you should leave it. to change the default you need to test all the packages that it might break
<lle-bout>ennoausberlin: you can use 'guix search python-pytest' and look at the location field to figure out what module to bring into scope
<ennoausberlin>le-bout: Great advice! It now fails while building but at least the scheme package definition is fine.
<guixy>I just ran ddrescue. It didn't tell me anything about the targeted device other than that it seems healthy...
<guixy>I'm looking for what information it has. strings has revealed it has many long strings (over 100 characters long) that look like source code, (some guile scheme and some C) but I can't conclude anything about the structure...
<guixy>bye guix
<rekado_>I use testdisk for recovering deleted files.
<cdegroot_>TIL that a channe repo gets scanned recursively for scheme source code and "non-channel" .scm in there result in seriously dense build errors.
<cmack>good morning, I'm trying to boot the guix image from usb on an older non-EFI machine but without success. Is the image built with legacy bios support or do I need to build my own image for this?
<lle-bout>cmack: it is built with legacy bios support
<lle-bout>cmack: did you use dd?
<leoprikler>cdegroot_: yep, you better hide your news.scm
<cmack>lle-bout: yes
<cdegroot_>leoprikler: I've been digging for hours before I realized that the errors pertained to some other scheme files. Moved the channel stuff into a subdir, safer :)
<cmack>although fdisk is showing "Empty" for Type
<bone-baboon>I am working on overcoming two hurdles that are in my way of using Guix.  Which after considering several other\
<bone-baboon> options is the operating system I want to use.  Runners up were Gentoo, OpenBSD and Devuan.  However Guix has \
<bone-baboon>attractive features that these others lack.
<bone-baboon>The first hurdle is getting X server to work.  I have asked for help on the mailing list about starting X with \
<bone-baboon>`xinit`, `gdm` and `startx`:
<bone-baboon>The second hurdle is installing a previous version of a package.
<bone-baboon>Help with either of these would be appreciated. Thank you
<i1l>bone-baboon: sway wm? closest to xinit. just `sway` from TTY. needs elogind (if not suid).
<i1l>bone-baboon: 2-nd is called inferiors in the manual.
<lle-bout`>bone-baboon: older versions of packages can be installed with the 'guix time-machine' command, e.g. guix time-machine --commit=<hash> -- install <pkg>
<nefix>so, in theory, the patch is sent. I'm not sure if I've followed the right steps or if I configured git-send-email correctly...
<bone-baboon>sneek later tell i1l I will try Sway and Wayland. I read the Inferiors section of the manual and tried modifying the example given but I get an error that I posted to the mailing list.
<sneek>Got it.
<lle-bout`>bone-baboon: time-machine does not work for all previous revisions of GNU Guix, it's still a recent feature I think too far back it doesnt work
<lle-bout`>time-machine or inferiors
<bone-baboon>lle-bout`: Thanks.  I was running into an error when I tried to use Inferiors see the mailing list link I posted above. I will try time-machine.
<lle-bout`>bone-baboon: my advice is that you attempt other revisions that still contain a version of the package you want
<bone-baboon>lle-bout`: What do you mean by other revisions?
<lle-bout`>bone-baboon: other commit hashes
<bone-baboon>The package I am trying to get is openvpn@2.4.9
<bone-baboon>So in this case commit hash: c5a2b70135c9830e9c3051ddf4a096f9a80eb952
<lle-bout`>bone-baboon: until right before the update to 2.4.10 openvpn is still available at version 2.4.9
<lle-bout`>That's plenty of commits to choose from
<lle-bout`>raghavgururajan: hey so what's next for GNOME you think?
<bone-baboon>lle-bout`: Thanks for clarifying that.
<lle-bout`>civodul: so many things come to meaning with guix-explorer, can't thank you enough, still can't use it on my config but using examples
<lle-bout`>civodul: I realize the shepherd service things are actually really simple
<Rovanion>I'm working on the sendmail package and think I managed to do something right. Two questions though: 1. what is a helpfile and 2. where should sendmail stats go?
<civodul>lle-bout`: aaah! assuming you're not saying this just to please me ;-), that makes me happy!
<lle-bout`>civodul: I really do not, I've been exploring things since around an hour now
<civodul>heh, i do find it hypnotizing
<lle-bout`>civodul: the graph is too big some times it doesnt fit on the screen but there's workarounds
<lle-bout`>civodul: you should make a blog post about it!
<lle-bout`>civodul: or when it's within GNU Guix proper
<civodul>i'm sure with some more d3.js hacking we could improve graph rendering, when there are many nodes
<Whyvn>I am wanting to make a package that I need some clarifcation on to clear some confusion. The steps are: git clone, cd into cloned dir, mkdir build, cd build, cmake .. -DBUILD_STATIC_DEPS=ON -DBUILD_SHARED_LIBS=OFF -DSTATIC_LINK=ON, make -j$(nproc). Now i know there is a mkdir-p and also a chdir function, but i am confuesed by the cmake .., would I override the install phase and chdir back to root and then run cmake with the
<Whyvn>confgiure-flags and then chdir back into the build dir and run make with the configure-flags -j$(nproc)?
<lle-bout`>civodul: maybe also pretty rendering of generated executable Scheme files
<civodul>oh sure
<lle-bout`>civodul: also in your talk, parameters, very elegant solution I like it a lot
<civodul>yeah it can be pretty nice but has to be used with care, due to combinatory explosion
<lle-bout`>Whyvn: what are you trying to do?
<civodul>cbaines: i'm testing and will commit if everything's ok
<cbaines>civodul, OK
<lle-bout`>bone-baboon: about xorg, look at this too:
<Whyvn>lle-bout`: create a package for
<cbaines>civodul, I don't know if you've seen if you have any advice though, that might be useful, I need to have another go at fixing things at some point
<civodul>cbaines: ah yes, i did see that message and i think my immediate reaction was to look away :-)
<civodul>i'll take a closer look
<cbaines>haha :)
<lle-bout`>Whyvn: I can't take arbitrary package requests and commit to doing them because there's lots to do in GNU Guix and I want to feel free to set my own priorities but this looks like an easy one to package
<cbaines>Before separating out the connection caching from the substitute related code in Guix, I was putting some of the errors in the Guix Build Coordinator down to shared cached connections, but now that's not an issue, it's clear that something's up with concurrent HTTPS connections in Guile
<civodul>or GnuTLS
<civodul>or the mixture of both :-/
<cbaines>yeah, I'm really hoping this isn't an issue in GnuTLS, especially as there's a statement that things should be fine with threads (although under particular conditions)
<Whyvn>lle-bout`: I had more of a question on the step sequence. with the moving back and forth through the directories. would i just override the install phase or is there other phases i need to condsider?
<civodul>d'oh, "guix weather" tells me we're at 95.2% for x86_64!
<civodul>i think it's never been this good, even for x86_64
<civodul>or rarely
<Rovanion>lle-bout`: I think I did some good for sendmail:
<lle-bout`>Whyvn: sorry didnt link with my previous question
<lle-bout`>Whyvn: what is the problem you're encoutering? can you send your current package definition?
<lle-bout`>Rovanion: thanks a lot for working on it!
<lle-bout`>Rovanion: one thing, the commit message is not compliant, but I am about to suggest you a correct version on the bug
<lle-bout`>Rovanion: See and and examples in the current commit history of GNU Guix
<civodul>80% of substitutes on aarch64-linux, woow
<civodul>cbaines: i can reproduce the crash with 10 threads
<cbaines>civodul, but not with just two?
<lle-bout`>civodul: ah wow aarch64-linux!
<civodul>cbaines: with two it seems to be okay
<civodul>i tried "rr record -n guile /tmp/threaded-https-connections-test.scm", but unfortunately rr crashes :-/
*civodul -> dinner break
<cbaines>civodul, there's a (iota 512) bit, and if you're not seeing it crash, I'd increase that number.
<lle-bout`>Rovanion: so you actually added more unrelated m4 defines and it worked..? o_O
<lle-bout`>Rovanion: based on the old package definition I think you can figure out where helpfile and statistics file go:
<lle-bout`>Rovanion: smrsh is still missing somehow but great work! continue!
<lle-bout`>I had gave up
<bone-baboon>lle-bout`: thank you for pointing out `xorg-server-service-type`.  I will give it a try it.
<Rovanion>lle-bout`: The error messages in the bulid log was about `mkdir -p /etc/mail` failing so I went through the build scripts trying to find where it could possibly be doing that. And it seems to have worked.
<Rovanion>lle-bout`: Thanks for the paste!
<lle-bout`>Rovanion: I see! They were silently ignored it seems, I couldnt find them myself.
<lle-bout`>Rovanion: I also made a complete answer to your bug
<soouul>anybody here use wayland? im trying to compile a program and i do have the dependencies but pkg-config cant find them :c
<Whyvn>lle-bout`: this is what i have so far. my confusion is if the cmake is correctly states, and how I would run make -j$(nproc) after cmake
<Whyvn>correctly stated
<lle-bout`>soouul: how do you compile that program?
<soouul>its looking for wayland-client
<lle-bout`>soouul: with GNU Guix or manually?
<lle-bout`>soouul: did you use the guix environment command?
<soouul>oh? WHAT
<lle-bout`>wayland-client is included in the wayland package
<soouul>yeah i have it but it cant find it
<soouul>idunno why
<soouul>perhaps cuz its installed globally?
<lle-bout`>soouul: you can do: guix environment --ad-hoc wayland pkg-config
<lle-bout`>it spawns a temporary shell environment with those packages available
<lle-bout`>You can add more also, like meson
<lle-bout`>Just expand the list
<lle-bout`>You can also have a oneliner like: guix environment --ad-hoc wayland pkg-config meson -- meson <whatever>
<Rovanion>lle-bout`: Thank you!
<lle-bout`>Whyvn: I don't think using (loki-network) at the end works, use loki-network alone without parenthesis instead
<lle-bout`>the hash of the source appears wrong
<soouul>yeah i think i gotta install wayland-client for myself
<Whyvn>lle-bout`: hrm, i used guix hash -rx is that wrong?
<lle-bout`>Whyvn: cmake stuff looks OK! make is run automatically in a default 'build phase so do not worry about that, just run it now and figure errors out
<soouul>nvm i dont know what it is
<soouul>with environment it does work
<Whyvn>lle-bout`: how can I add the -j$(nproc) to the make command? thanks for looking at it
<lle-bout`>soouul: In GNU Guix, not all packages are available in the global environments, e.g. sway can require wayland while not poluting the global system profile environment with it
<lle-bout`>environment allows you to explicitly specify the packages you want available in the spawned shell environment, by the way to quit just use CTRL-D
<soouul>so basically i can get away with compiling in an environment and not actually having those dependencies on my system?
<lle-bout`>Whyvn: it's automatically added, controlled by #:parallel-build? field
<lle-bout`>by default that field is #t (true)
<lle-bout`>soouul: yes, but beware if you use 'guix gc' the built binaries might break, that's why it's preferable to create a package definition or have a profile somewhere (which can also be used with environment) so that it's protected from garbage collection by being registered as a gc root
<lle-bout`>soouul: basically the built binaries will have absolute paths to /gnu/store/... in them, if you use 'guix gc' these paths might be deleted, so that's why the binaries could break
<lle-bout`>registering as gc root means the store items wont be deleted when using 'guix gc'
<soouul>wack, so basically i should just make a package myself?
<lle-bout`>The ways to register as gc root, is by including them in a profile
<lle-bout`>soouul: yes, you can write one with Scheme code or JSON even if you are at better ease with that, note however that JSON is less powerful and some things you will not be able to do with it.
<soouul>its a wayland utility so at that point, if i do end up packaging it, i might as well commit it? lmfao
<soouul>like make a pr
<lle-bout`>soouul: yes of course!
<lle-bout`>soouul: what is it?
<lle-bout`>soouul: it looks easy! do try packaging!
<lle-bout`>soouul: if you have any question, ask I will answer
<soouul>well i just compiled it
<soouul>then ran guix gc
<soouul>and then ran it again because you know
<soouul>and it works! but still imma package it, this feels janky as hell
<soouul>in my conscience i mean
<lle-bout`>soouul: it might be because other packages in your various user or system profiles register the dependencies of wlsunset in a gc-root
<lle-bout`>that's luck
<soouul>yeah thats what i figured
<soouul>i mean, i am using wayland after all and that package has like no dependencies
<lle-bout`>soouul: note you can embed package definitions in your system configuration
<soouul>that makes sense
<lle-bout`>it's just code and the packages field takes a list of package objects, so you can just define one above and use it down there
<soouul>thats sick
<lle-bout`>but I do encourage you submit it to GNU Guix also
<lle-bout`>in the mean time (pending review) you can use the package definition this way in your system configuration
<soouul>the niceties of open source
<soouul>in define modules i should leave it as "gnu packages xxx"
<lle-bout`>soouul: what do you mean?
<lle-bout`>first, if you are preparing to contribute to GNU Guix, do you have a git clone of GNU Guix built?
<soouul>the first line in the packages example is `(define-module (gnu packages hello))`
<soouul>no, i wanna figure out how it works first
<soouul>i see now that, i dont need the define-module thingy
<soouul>since im gonna commit it to an existing package anyways
<lle-bout`>soouul: you will be adding wl-sunset to an existing module probably yes
<lle-bout`>but you otherwise do not need modules if you are making an out of tree package
<lle-bout`>soouul: the out-of-tree package just has to contain the (package ..) object, nothing more
<lle-bout`>to bring modules into scope, use (use-modules (gnu packages ...) (guix download) ...) for example
<soouul>gotcha, thanks
<lle-bout`>if you read at the "-f" option you will what I am talking about, you can also use this option with install and environment subcommands
<soouul>yep, i see it
<soouul>u so smort
<lle-bout`>soouul: for environment actually it's -l instead not -f
<lle-bout`>Whyvn: since you use a git-reference in your package definition, guix hash doesnt work, also you should use guix download rather, but for git there's no subcommand, so what I do is I run the build then copy the actual hash from the error and feed it in.
<lle-bout`>I am not sure of the technicalities of how git-reference is hashed and it seems there's no subcommand to reproduce that behavior.
<soouul>how do i get the sha256 of the package?
<pkill9>guix hash
<nckx>lle-bout`: guix hash -rx
<lle-bout`>soouul: what I do is I get it from the error when it happens, it prints the hash it got
<nckx>lle-bout`: <guix hash doesnt work> When?
<lle-bout`>nckx: is that for git-reference? I remember trying and it didnt produce what was expected
<nckx>Well, I don't know what you were expecting, so can't say. It prints the value expected in the origin's hash field.
<lle-bout`>nckx: yes that is what I am talking about, I'll try again but it didnt work when I tried to do that, thanks. Also what about tarballs? Can I generate the hash without using "guix download" with guix hash?
<nckx>That's why it exists.
<lle-bout`>nckx: It never produced the outputs expected in the origin fields for me, but I'll try again.
<nckx><guix hash doesnt work, also you should use guix download rather> They are the same, so something is wrong.
<nckx>Basically your whole response to Whyvn sounds like something went wrong in a confusing way for you once, and we should find out what.
<lle-bout`>nckx: not only once but yep, that was when I was still a complete stranger to the project and I asked here several times and got no answers so I resorted even until now to workarounds
<nckx>That's still quite a leap to ‘guix hash doesn't work on git checkouts’. It's documented to, and the manual explains how to invoke it.
*nckx tests.
<lle-bout`>I can't recommend what I didnt use and havent seen working, so that's what I felt was the most appropriate to answer for me
<nckx>Works here.
<nckx>Well, if you didn't use it...
<nckx>I don't know what to say.
<lle-bout`>nckx: I did use it but it wasnt producing the expected outputs
<nckx>lle-bout`: On which input?
<nckx>I would like to debug this.
<nckx>I'm currently trying random hashes + git checkouts already in Guix, which isn't a very efficient way to do so :)
<nckx>Is it possible you had generated files in the checkout?
<lle-bout`>nckx: I didnt have any generated file in the checkout, however now that I am thinking it may be the .git
<lle-bout`> - I am trying with this
<soouul>wait if i put im using the meson build system, i dont have to put meson's module right?
<nckx>The purpose of ‘-x’ is to filter out .git (it's a hard-coded list IIRC, not ideal but good enough).
<nckx>lle-bout`: Thanks.
<lle-bout`>nckx: hmm I dont think I used -x earlier
<nckx>Mystery solved.
<lle-bout`>soouul: you have to bring (guix build-system meson)
<soouul>i did do that!
<lle-bout`>nckx: with "guix hash -rx" it works, thanks
<lle-bout`>nckx: don't think that existed when I first was looking at it:
<lle-bout`>3 years ago
<nckx>lle-bout`: It would still have been mentioned in the --help output. Anyway. It must have been a memorably frustrating experience not to receive answers here that you thought guix hash was broken for 3 years. Genuinely sorry about that.
<nckx>I hope we're doing better now.
<lle-bout`>nckx: this will be helpful, because I otherwise felt quite uneasy not being able to check the signature of tarballs or git tags if they exist before putting a hash in a guix package definition, even if it's still useful in TOFU mode
<soouul>how do i make it so the build system takes no arguments? #f is not working
<soouul>should i just put ()
<lle-bout`>nckx: heh
<soouul>nvm just delete the line lmao
<nckx>soouul: Hmm? I haven't been following your thread but few fields are mandatory.
<soouul>thank u
<soouul>didnt know that was allowed
<nckx>No, thank you.
<nckx>You figured it out.
<nckx>Thought maybe you were inheriting something.
<lle-bout`>soouul: as general advice, reading other package definitions in GNU Guix is great help resource
<lle-bout`>git grep for stuff
<soouul>thats what i did!
<soouul>and also the documentation
<soouul>was looking at dunst package for this one
<lle-bout`>nckx: it wasnt clear at the time that GNU Guix wasnt including the .git in the checkout, how all that worked was still confusing and unclear
<lle-bout`>as in, it was cloning things "bare"
<lle-bout`>or deletes it after, I don't know
<lle-bout`>shallow clone or something
<lle-bout`>soouul: great!!
<nckx>lle-bout`: Right. Both; it tries to shallow clone but that still creates a .git, so Guix has (delete-file-recursively ".git").
<soouul>weird, i did the hash thing you told me but it keeps saying im using the wrong one
<soouul>ran gc and everything
<nckx>soouul: Could you give more details?
<lle-bout`>soouul: so you cloned the repo? you checked out to the right commit (or version tag/branch), then ran guix hash -rx <path/of/clone>?
<nckx>Does ‘git status’ report any untracked/unstaged changes?
<soouul>i didnt do what lle-bout` said :(
<soouul>so lemme try rq
<nckx>You should do what lle-bout` says.
<soouul>yeah no, i did do it from the error and from what you told me
<soouul>gives the same hash but not working
<soouul>lemme try sumthing rq actually
<soouul>yup, im idiot
<lle-bout`>nckx: I think 'guix download' is not a good mechanism, because it doesnt allow you to verify hashes with another format or check signatures
<soouul>i did not do it properly and its working now :DDD
<lle-bout`>soouul: awesome!
<nckx>lle-bout`: Yes, it's very (too) limited.
<lle-bout`>nckx: it doesnt print the path of the store item, from which you could do verification afterwards even though it would be great to do it before actually adding it to the store
<nckx>I think it does what it does well, it should just handle more input.
<soouul>I DID IT, it WERKED!
<lle-bout`>soouul: yay!
<nckx>lle-bout`: <it doesnt print the path of the store item> There you go again, I don't know what to say. Are we even talking about the same tool?
<nckx>guix download → store name\nhash
<lle-bout`>nckx: why do you say you don't know what to say, you could just say it does
<nckx>Because I'm confused?
<lle-bout`>nckx: in my memory it printed just the hash and it has gotten me puzzled and stuck before but somehow now it doesnt just print the hash >.>
<nckx>In the context of discussing x's design flaws, to someone saying ‘x doesn't y’, simply saying ‘yes it does’ is lazy and assumes that person doesn't know what they're talking about.
<lle-bout`>nckx: I think you can say that it does do it for you
<nckx>First you said it didn't work, then you say it needs improvement (true) because it doesn't do something that's trivial to check on your end.
<nckx>It is not very respectful of my time.
<lfam>Does anyone have ideas about <>?
<soouul>lle-bout`: everything on this part of the docs
<soouul>is still accurate right?
<lfam>There are some recent updates, soouul
<lfam>The basics are still correct, though
<lle-bout`>nckx: I feel more uneasy when you say you don't know what to say than what I suggested
<soouul>do i still have to build the --pure environment though?
<nckx>lle-bout`: I genuinely don't. All good though.
<soouul>or maybe its easier to know whats different
<lfam>soouul: Are you just asking about how to build Guix?
<lle-bout`>nckx: I don't have a shell in my mind so some times I say wrong things or remember wrong it's normal
<soouul>nop, contributing
<soouul>i am running GuixSD
<lle-bout`>soouul: yes still accurate
<soouul>oki, thank you!
<nckx>lle-bout`: Then it's better to ask than to declare.
<lle-bout`>soouul: --pure yes it's important
<nckx>soouul: Yay!
<lfam>Regarding #47428, the root user's Guix is up to date and the recent copy of the manual is already built in /gnu/store
<lfam>But, it's still not updated on the web site
<lfam>We need to figure this out
<lle-bout`>nckx: when I send email I check things more, but in IRC like I speak IRL I am not relaxed about checking what I am saying always
<lle-bout`>I am relaxed *
<nckx>lfam: <So, maybe we just need to update and reconfigure, and try again.> Is that still the question?
<lle-bout`>I used to be more rigorous in everything but I stopped because that's also a mental health issue for me, so put myself to unrealistic levels of exigence at all times
<lfam>nckx: Yeah, I guess so. It's not clear to me how the server is being managed though, so I'm scared to reconfigure it
<nckx>lle-bout`: There's the problem. I'm never relaxed. I'm always on edge. I think it has something to do with being subscribed to GNU mailing lists without alcohol in the house.
<lfam>Laugh or cry?
<soouul>laugh so you dont cry
<nckx>{that laughing through tears emojo I'm too lazy to look up}
<lle-bout`>lfam: no idea nope
<soouul>do you guys use a vpn? if so which one? i have been eyeing one for a while now but still cant pick
<nckx>lfam: It's not that scary (although I can't say it's best practice city, either). I can reconfigure if that will help?
<lfam>As far as I can tell, the current-system of is up to date, as well as root's current-guix
<lfam>So, I'm not sure what is wrong
<lfam>Maybe I can find the cron logs
<lle-bout`>soouul: I use Mullvad's wireguard servers with NetworkManager wireguard support (without their Electron client) it works great
<nckx>lfam: ...owkaay.
<lfam>Did that work? ;)
<lfam>write(1) is not installed
<nckx>lfam: It worked and scared the hell out of me.
<soouul>lle-bout`: yeah i was thinking of mullvad, seems nice
<lle-bout`>soouul: it really cares about privacy because it only asks for an account number and you can buy vouchers with cash in shops so payments can also be untracable
<lle-bout`>soouul: but I don't say that works well for a VPN, at that level of worrying probably better to use Tor
<soouul>ye, i used to use PIA, but it seems its not as good nowadays
<soouul>yeah, im not that worried! just want a nice vpn
<lfam>nckx: We should look into rotating the mcron.log
<lle-bout`>would be nice if network-manager service supported dispatchers
<soouul>wireguard-tools for the network-manager support right?
<lle-bout`>soouul: with Linux 5.6+ wireguard is in the kernel
<soouul>oh its right there
<lle-bout`>soouul: I didnt have to install any wireguard things besides linux with network-manager to have it work IIRC
<nckx>lfam: Weird, it should be in util-linux. ‘Should’. Not in ours.
<nckx>Disabled legacy?
<lfam>Well it's not important
<lfam>I just thought it might be fun
<nckx>lfam: Yes, well spotted, we should look into rotating the 78-gigabyte log file, good point.
<lfam>I was like, why is it taking so long to open?
*oreoking[m] uploaded an image: (6KiB) < >
<oreoking[m]>Why is guix not building?
<lle-bout`>lfam: aha
<lle-bout`>> when you have so much disk space 78GB log files arent raising any alarm
<lfam>And so much RAM
<nckx>oreoking[m]: I don't know, what does that log file say? (Use bzless to view it, if you can't read raw bzip2.)
<lfam>oreoking[m]: There was a broken version of that package. You should do `guix pull` to make the fixed version available
<lfam>nckx: I think it was a test failure that accidentally got "packaged"
<nckx>lfam: Really? When?
<lle-bout`>oops sorry actual users affected by my broken commits
<lfam>Couple days ago
<lfam>The current revision is 18-6e7ba45
<lfam>Anyways... back to the the berlin server
<lfam>I don't think the log file is the problem, although it makes it difficult to inspect the cron outputs
<lfam>I wonder, can I invoke the service "by hand"?
<nckx>lfam: I see you still have mcron.log open, so will keep it around for now?
<lfam>It should be closed now
*nckx unpauses rottlog.
<lfam>If it's still open, then it's being held open in a virtual terminal that I've closed
<lfam>Shall I kill PID 25728, nckx?
<lfam>I think that was me
<nckx>So I've added a rottlog rule to berlin.scm on berlin, but haven't even committed it because it's probably not the right place. Should be a default, no?
<nckx>lfam: It was vi, so go ahead, although it can't hurt much (just waste space until it dies).
<lfam>I noticed you adding the rottlog job for mcron.log. I think it's right enough
<lfam>It should be a default, though, you're right
<nckx>I'm too tired/not in the mood to submit patches tonight.
<nckx>‘It'll do.’
<lfam>Thanks for doing that
<nckx>That file was 71 times the size of my hard drive growing up. It was disgusting.
<lfam>I'm going to file a bug about how mcron should use the rottlog service
<nckx>Poor rottlog is still chugging through it.
<nckx>I've added a comment.
<lfam>Next step... try reading the rotated logs :)
<lfam>One step at a time
<lfam>We should probably make a similar adjustment for cuirass-web.log
<lle-bout`>lfam: does it also compress logs rottlog?
<nckx>It gzip-compresses them without adding a .gz extension, which is a bit meh, but fine.
<nckx>lfam: Well, it's still going to be one giant file now.
<lfam>Yeah... it should add the .gz
<lle-bout`>it's definitely mehhh
<nckx>Just so you know.
<lfam>I can use `split`
<lfam>It's already written >1 GiB to the new log
<lfam>Kind of crazy
<lle-bout`>hmm some problem here
<lfam>Or maybe it's writing the "rotated" logfile, not sure
<oreoking[m]><lfam "oreoking: There was a broken ver"> guix pull is not working
<lfam>How is it failing?
<oreoking[m]>its failing
<nckx>oreoking[m]: That's not helpful. Please elaborate.
<lfam>To be fair, we sent our messages at the same instant. They weren't replying to my question
<nckx>I have only minute granularity and the choice of words was coincidental.
<lfam>I just ran `guix pull` and it succeeded
<lfam>oreoking[m] ^
<nckx>lfam: Is there a specific reason your bug report is as non-specific as it is?
<lfam>Which bug report?
<nckx>About mcron logz.
<lfam>It's just a feature request. "mcron should use logrotate"
<lfam>Got 2 go
*oreoking[m] uploaded an image: (7KiB) < >
<oreoking[m]><nckx "oreoking: That's not helpful. P"> here
<oreoking[m]>guix pull wont succeed
<nckx>And I responded: <nckx> oreoking[m]: I don't know, what does that log file say? (Use bzless to view it, if you can't read raw bzip2.)
*nckx AFK.
***aidalgol_ is now known as aidalgol
<pranavats>Hello, is anybody using emacs-native-comp from ?
<pranavats>I installed it from that channel and I'm getting the error: "Cannot open load file: No such file or directory, comp".
<pranavats>I was wondering if anybody else faced this issue.
*oreoking[m] uploaded an image: (10KiB) < >
<oreoking[m]><nckx "And I responded: <nckx> oreoking"> here
<rhou[m]>what does this mean from linter: `sentences in description should be followed by two space`?
<oreoking[m]>thats what happened when i use bzless on logs
<jx96>VGA output doesn't work with Guix + GNOME, but it works on other distros (including Parabola/Trisquel).
<nckx>oreoking[m]: Thanks. Your problem is with a third-party channel (maybe pkill9's, they are a regular here but not currently on-line) that is still using the removed qt@4. The owner needs to fix it.
<vagrantc>rhou[m]: The description should have sentences followed by two spaces. Like that <---. Not like this. Or this.
<jx96>Suspend with Guix System + GNOME is broken for some reason. Also works in other distros.
<rhou[m]><vagrantc "rhou: The description should hav"> so you have to put a space before a period?
<nckx>oreoking[m]: You could lock your guix channel to commit 0d8cea4f247272a36c307276253f014f271f1b56 in your channels.scm. You won't get security updates (if any) so don't forget to remove it as soon as the conflict is resolved.
<nckx>rhou[m]: No, two after.
<vagrantc>rhou[m]: two spaces after the period, unless it's the last sentence.
<nckx>‘Hello. I am nckx.’
<nckx>‘Hello. I am nckx.’ <-- not this.
*roptat is building scala again
<rhou[m]>ok gone try it out, kind of unusual tho...
<nckx>It's more unusual now than it used to be.
<vagrantc>rhou[m]: it's a pretty pendantic stylistic preference, i'll agree. :)
<nckx>I grew up doing it & still do, especially after switching to emacs.
<jx96>And some GNOME vector icons (Web, icons in the settings and menus)
<jx96>I just want to know if anyone can reproduce these bugs.
<nckx>jx96: I've noticed some SVG icon corruption (e.g., the ‘pen’ icon in Evince has wings). Don't use GNOME.
<mprofessor>QQ: Am I gonna run into issues if I install guix on a computer with Nvidia graphics?
<nckx>mroh: I think so, if your card is in any way recent. I don't think any modern PC graphics cards have free drivers anymore, and certainly not non-Intel ones.
<nckx>Sorry, mroh, meant mprofessor.
<pkill9>well, for 3D accelerated graphics
<nckx>True, although even 2D is a crap shoot.
<mprofessor>Hmm. That's a bummer. So y'all have AMD graphics?
<nckx>Intel. Old.
<pkill9>intel also
<nckx>‘i915: it's acceptable™.’
<pkill9>that's some very modest marketing
<mprofessor>Intel didn't make sense to me anymore last time I upgraded, went with Ryzen and Nvidia.
<mprofessor>Only learned about the driver issues while reading an article about wayland.
<pkill9>oreoking[m]: I removed the snowman package from the pkill9 repository, which referenced qt-4, so should work now
<nckx>mprofessor: Don't be fooled, new (and I've been saying that for so long it's hardly ‘new’ now) AMD graphics are no more free than nvidia.
<pkill9>why is that nckx?
<nckx>IIRC they require proprietary firmware? We had great troubles getting one of the previous Guix releases to display the installer.
<nckx>To my great disappointment, not a 3D experience.
<nckx>pkill9: This is from 2019 but is my experience as well
<nckx>I happened to have an AMD gfx laptop when the installer first came out & refused to work on it. Decided to get rid of it by accidentally spilling water on it. Was a good decision.
<sneek>jonsger, you have 1 message!
<sneek>jonsger, mothacehe says: you may want to update to the latest Cuirass version (1.0.0-3.f5a2eea), otherwise some evaluations may fail (
*lle-bout waves
*midnight waves back
*lle-bout needs to redo their system and user configuration in a proper way also with something like guix-home or guix-home-manager