<pashencija[m]>What file in the repo do I put the package? It's a simple GUI note taking app
<KarlJoad>podiki[m]: The script just resets my monitors, because one of them is stupid and is not picked up by X to nicely for some reason. So, xrandr fixes that. So a package generating the Guile program makes more sense in that case?
<pashencija[m]>> What file in the repo do I put the package? It's a simple GUI note taking app
<pashencija[m]>Like I packaged FeatherPad to text-editors.scm. However, note taking app is not a text editor, so I need another place
<podiki[m]>I don't think it will matter much, sounds pretty simple as either a bash script as a package (xrandr input, you don't need to install xrandr then) or package that makes that little guile script. I don't have much experience with the latter
<podiki[m]>but if you wanted to learn guile scripts, sounds like a nice little project
<nckx>pashencija[m]: task-management.scm? (Bit funny in its bombast, but hey.) Or you could create a new notes.scm.
<nckx>It's more apt than text-editors.scm for sure.
<kabouik>I initially thought those issues were due to another package I was trying to get working (Discord), but I removed it from the private channel and the errors are still there. If I disabled my channels, errors are gone when doing guix pull. But I can't relate the errors to the only remaining package I have in the channel.
<pashencija[m]>kabouik: Your discord package uses binary from the website, right?
<pashencija[m]>If so, double check the code related to enumerating architectures
<KarlJoad>lilyp: Is there going to be a post about the outage? I'm curious what happened.
<kabouik>The Discord package is gone temporarily pashencija[m], so the errors are not due to it (but it will bring some more)
<kabouik>It's based on the .tar.gz from the website by the way
<kabouik>Yes I'm not posting about it, just wanted to elaborate what I thought was the issue, then removed this package.scm, and still got issues on the remaining package which yet used to build fine some months ago; and I don't see the link between that package and the error I'm getting in the logs.
<pashencija[m]>kabouik: It should! Guix clones local repo and switches to the latest commit of the predefined (in channels.scm) branch
<kabouik>That's a good question; something I was probably advised to do 7 months ago without fully understanding; but it did build at the time (I have nnn installed from this package still). But I am not sure how the errors still refer to discord while the scm file has been deleted locally and remotely
<kabouik>Is there anything to do to optimize guix operation times?
<kabouik>I started `guix install steam firefox` hours ago and then wanted to install a couple other things that came up to my mind minutes later, but I can't since guix is busy, and I'm out of ideas of what to do while waiting
<kabouik>(Wish guix could roughly predict how long an operation will take, at least, but I know this is difficult; the problem is the time it takes is not the same order of magnitude as package managers I'm used to, so I didn't expect there would be such inertia between my commands)
<kabouik>But I think I'm just not used yet to how long building everything can be (I've never used Gentoo for instance), and don't know how to predict when an install will need many dependencies to build
<podiki[m]>you can see the "guix weather" command to see substitute availability
<kabouik>Oh, you're absolutely right, thanks! And sorry for the confusion, my bad.
<podiki[m]>though with some issues this past week some things are a little behind
<kabouik>I just read about substitutes on the web some minutes ago, still reading to understand what they are. I assume they are like precompiled dependencies that may or may not be up to date to the latest versions available
<podiki[m]>assuming you are trying to build what has been built on the build farm, with substitutes you will just download the result instead
<podiki[m]>(done by the build hash to know if it is the same or not)
<podiki[m]>anyway, gotta get going, but if you don't want to compile everything, generally you don't have to
<kabouik>Actually if I had noticed icecat was there, I would have picked it over Firefox. I use Nyxt as my browser anyway, but wanted a backup one because Nyxt is not very stable yet. However I don't think I can cancel my Firefox install without losing the other packages I installed at the same time, so I'll wait until it ends.
<podiki[m]>you would only lose any progress in what is currently being built, I think everything else built/downloaded will still be in your /gnu/store to be reused if needed (unless you do a garbage collection of course)
<kabouik>So substitutes are automatically picked by `guix install xxx` if xxx has a matching hash substitute? That's nice, and now I know I can use guix weather to check if this will be quick or not (even though I can't predict how *not quick* it may be when no substitutes are availabel).
<podiki[m]>as long as you have substitutes enabled, which I think is the default
<nckx>kabouik: Running multiple ‘guix install‘s in parallel used to be possible, but it was deliberately disabled. It still works with ‘guix build’, however! The builds will still happen in parallel, and you can almost instantly ‘guix install’ the result later.
<nckx>Still can't say I understand the rationale for that big ‘guix install’ lock, but it's easy to work around.
<nckx>issues.guix.gnu.org is now synchronised with debbugs.
<nckx>Thanks to rekado for the dirty secret behind *that*…
<nckx>kabouik: <So substitutes are automatically picked by `guix install xxx`> To add to podiki[m]'s answer: you also need to make sure that the public key is authorised, or Guix will not trust the server even if present in the list of URLs. This is unfortunately the case with bordeaux if you installed from 1.3.0. If ‘grep 7D602902D3 /etc/guix/acl’ returns nothing, you're missing out on FREE substitutes included in your subscription, and you should add it (
<nckx>I understand that lock_wait && build && mkprofile && unlock is simple (and therefore safest) to implement but I think it's much more restrictive than is needed to protect against that. It wouldn't matter if builds didn't take hours. They just make that very obvious.
<nckx>I mean, the obvious work-around is to literally move the build part outside of the lock by hand, there's no reason Guix couldn't do that, but it would add a little bit of complexit (roll-backs waiting for extra locks).
<nckx>That's not mine. It was just a conversation with Ludo'.
<nckx>It's not *hard* to implement, but it seemed clear that it wouldn't convince him.
<unmatched-paren>Ah, issues.guix.gnu.org is working now. The magic cable's been plugged in, I guess :)
<nckx>Ah, ditto here: ‘IMO, there’s no reason to run multiple ‘guix package’ on the same profile concurrently. With a wait-for-lock policy, the result would be non-deterministic: you cannot tell which one of the two processes will complete first.’
<nckx>I literally don't know how to argue with that.
<nckx>unmatched-paren: More like the magic rsync-bash-loop-running-in-GNU-screen.
<sailorCa`>Hi, could you please help me with the `guix build` command? I think I miss something basic. My expectation: I can write a file, i.e. repo/packages/npm.scm, put a package difinition here and then I can build it with `cd repo; guix build -L . package-name`. Also, please see my file: https://pastebin.com/XBm4PECM. In reality I've got the `guix build: error: npm-yarn: unknown package` error although `strace` shows me, that g
<nckx>jab: I never understood services and was frankly too intimidated to dive in until someone gave me a 10-minute 1-on-1 chat in person at FOSDEM. We sorely need that kind of guidance in the manual, but I'm not the right person to write it.
<nckx>(It was actually a BoF session but I was the only B, which was great :)
<redsith>not long into the boot process, its a lenovo ryzen 3 system
<nckx>redsith: What I'd do first is edit your kernel command line by pressing ‘e’ at the GNU Guix menu entry in GRUB, and adding ‘nomodeset’ to the end of the line that starts with ’linux’, then pressinc C-x to boot.
<muradm>kind reminder for show stoppers: 56690 and 56699 seatd-service-type and greetd-service-type fixes.
<muradm>kind reminder: 56579 and 56608 fail2ban package and fail2ban-service-type
<muradm>minor reminder 56689 (mako update) 56688 (new package sworkstyle)
<Cairn>Hey, I'm having some trouble that I haven't seen before. I'm trying to run certain binary files, and I'm simply getting a `bash: ./program: No such file or directory` error. And of course, they're right there.
<oriansj>civodul: wouldn't the correct term be unpaid interns as we don't pay the workers?
<oriansj>and since they don't have a choice to work, wouldn't the more technically correct title be Slaves? Or would we be going with the Grandmaster term: "the prisoners with jobs" have resumed their tasks
<roptat>\o/ the French translation of the manual is at 100%
<oriansj>lilyp: well it is hard to add music to IRC but... Cheer up Brian, you know what they say? Some things in life are bad They can really make you mad Other things just make you swear and curse When you're chewing on life's gristle Don't grumble, give a whistle And this'll help things turn out for the best And ♫♫ always look on the gloomy side of life ♫♫