<ecbrown>jabranham: it's a good mirror. try it and see! :-) <jabranham>How can I add it permanently so I don't have to remember to type --substitute-urls="blah" every time? <pkill9>i created a franken-regex that attempts to convert a store path to a package into a 'package:output@version' format: sed -re 's/\/gnu\/store\/[0-9a-z]+-//' -e 's/\/.+//' -e 's/([a-z0-9\-]+)-([0-9\.]+)-([a-z]+)/\1:\3@\2/' -e 's/([a-z0-9\-]+)-([0-9\.]+)/\1@\2/' ***polarisfm[m] is now known as polarisfm
<rekado>efraim: phases should always return #t, even on failure. The invoke is just there to throw an exception when we need it. <jonsger>roptat: guix builds maven from source. So we don't use any of the binaries from upstream. Am I right? <ng0>btw: i've build the full rust chain here in less than 2 days. it's not that bad. :) *civodul was stuck in meetings yesterday and unable to get much work done :-/ <roptat>jonsger: we don't use any binary to get maven, but using maven means it will download binaries <roptat>/gnu/store/*/bin/maven is built without any upstream binary <roptat>but to build something, it requires a few plugins we don't have, so it will download them and dependencies from upstream <jonsger>have you any estimate how many hours did it take you to come so far? <roptat>I spent a few hours almost every evening for maybe a month or two <roptat>so I'd say between 100 and 200 hours <roptat>and I used work from hartmut too <roptat>which probably spared me another 100 hours or so <roptat>now I'm on many fronts: building maven plugins to have our own maven-build-system without any upstream binary, building gradle and other things unrelated to java <roptat>I feel like I've already spent as much time on these two than on maven itself... <jonsger>you do that in your free time, yes? or did you get paid for it? <roptat>I'd be happy to be paid for that though :) <jonsger>roptat: are you okay, when I share those information on a SUSE internal mailing list? <thorwil>how can i rebuild what `guix build --keep-failed` leaves in /tmp, for a package that already has a succesful build? <roptat>if it succeeded, guix removed the directory in /tmp <thorwil>roptat: during my work on gimp-resynthsizer, i used the files in /tmp to check paths in the makefiles <thorwil>roptat: i need to do that again, but `guix build` is rather stubborn about not investing any more work in a successfully build package ;) <roptat>you can run guix build --check -K <thorwil>`guix build --check -K --no-grafts gimp-resynthesizer` did the trick, thanks, roptat <janneke>civodul: how do we register for R-B, individually or as a group? <civodul>janneke: i think it's individual, though they probably set a limit on the number of people per project <janneke>civodul: OK, i'll try to register! yeah, i'd love to go! <civodul>that way you can spread the word about bootstrappable :-) <g_bor>civodul: I have just modified the Outreachy project description. <g_bor>I added some more specific requirements, added deliverables, milestones and communication advices. <g_bor>ok, I will wait for your feedback then <civodul>g_bor: i'd put the videos about the installation process as rather low priority <civodul>because it's something that's still in flux <civodul>regarding support for translation, perhaps we should be more specific? what do you have in mind? <civodul>i think we should write that we require the use of free tools for this job <g_bor>civodul: I guess I have written something about free tools. I will take the installation off board then right now, but we should think about how to pull in new users easily. <g_bor>Translation support would involve support for multiple subtitles, multiple audio channels, and a flexible timing setting for image data, to allow for varying length of text in different languages. <g_bor>yes, I put the free tools requirement in the additional information section <civodul>g_bor: i think we can keep installation (of GuixSD in particular), maybe just not make it the first item <civodul>g_bor: re translation, perhaps we could add exactly what you wrote above to the description? <g_bor>ok,I've also thought about it, I moved it to the last item <civodul>it seems i can't edit the description <civodul>i was wondering if we could add a bit of markup for bullet lists, etc. <civodul>because currently it's quite intimidating visually ;-) *civodul laughs while reading this in a commit of dannym: Rust 1.20.0 treats timestamp 0 as "file doesn't exist". <g_bor>ok, I've submitted the new version. <g_bor>Will have a look at formatting, but support seems to be limited <civodul>i see you're listed as the only mentor <civodul>i'm happy to co-mentor, but even happier if someone else steps up :-) <civodul>usually asking this kind of question ensures the channel remains silent ;-) <g_bor>actually you and rekado offered tot comentor, and it is nice. It seems that my wife is also willing to do so. <civodul>is your wife willing to co-mentor or to apply? (i thought the latter) <g_bor>The main question is who should be officially listed, and who are the ones that we would like to get involved. <g_bor>But actually there will be some times when we are going together, so someone might have to step in then. <jonsger>where does the money for the stipend comes from? is it from guix? <g_bor>One very important point is that the community have to agree on the content, so it would be nice if you or rekado could co-mentor, as I feel that we can reach consensus faster regarding the content. <g_bor>I've fixed up the formatting a bit, it is more visually appealing now. <rekado>g_bor: if nobody else steps up to co-mentor the project I’ll join you of course. I’d be happy if we could increase the number of people willing to mentor, though. <rekado>g_bor: thank you for making the changes to the proposal! <rekado>I agree that a video on installing GuixSD wouldn’t be the top priority. But building a virtual system with “guix system” might be covered by one of the videos. <thorwil>gimp-resynthesizer left stuff in ~/.guix-profile/lib/gimp/2.0/plug-ins but also ~/.guix-profile/lib/gimp/2.0/plug-ins/plug-ins <thorwil>after `guix package -r gimp-resynthesizer` it's still there!? <rekado>thorwil: you can check with “readlink -f ~/.guix-profile/lib/gimp/2.0/plug-ins/plug-ins” to see where it comes from <civodul>g_bor: thanks for improving the layout! <civodul>i agree with you rekado: an intro to 'guix system' in general would be nice <civodul>which in practice is similar to the installation procedure, just without the gory details about setting up networking, partitioning disks, and all that <janneke>does this guix offload test failure sound familiar? guix offload: error: build failed: implementation cannot deal with > 32-bit integers <rekado>janneke: I haven’t seen this before. <rekado>janneke: are both machines the same architecture? <janneke>the client should be ok, my laptop; it can offload to other servers <civodul>janneke: it's usually a daemon/client protocol error <civodul>could you strace both ends to see if there's anything obvious? <civodul>like "command not found", "file not found", etc. <janneke>ah! and strace the guix-daemon you mean? <civodul>"strace -f" guix-daemon on one side, and "strace -f" sshd on the other side <civodul>so that you can see what 'guix offload' sends on one side, and what the 'guile' process does on the other side <thorwil>why does `guix environment guix` warn about "guix environment: warning: failed to load '(#{.#gimp-resynthesizer}#)': no code for module (#{.#gimp-resynthesizer}#)"? <jlicht>thorwil: that seems like some temporary file left by your editor <civodul>g_bor: do you plan to go to the R-B summit? <roptat>civodul: g_bor, what's the time period for the internship and where can I read the description? <roptat>oh and a collegue of mine is interested in bootstrapping ocaml :) <rekado>oh, I guess one can only see details as either a coordinator, co-mentor, or internship applicant *janneke found it ... *really* silly: <janneke>-r--r--r-- 1 root root 188 Jul 13 15:54 signing-key.sec <civodul>still the error message could be, ahem, clearer <civodul>roptat: bootstrapping ocaml would be a nice project! though make sure you colleague would be eligible for Outreachy <roptat>I wasn't talking about outreachy and I don't think he's elligible <roptat>I can make modules like A{x=0;y=B.x} and B{x=0;y=A.x;x=1} <roptat>guess what values have A.y and B.y? <roptat>or if you print them in the other order, B.y: 0 A.y: 0 <civodul>circular module dependencies are bad as know ;-) <pkill9>i'm running `guix pull --commit=e67ad5532f76b53e955149da2f1e237696ff0893` but it keeps trying to compile it even though the berlin build server says it's been built here http://berlin.guixsd.org/eval/749 <rekado>pkill9: is berlin among your default substitute servers? <mbakke>What is the best way to check whether two strings denoting directories are the same, when they may or may not include a trailing slash? <civodul>mbakke: as a rule of thumb, don't do that <civodul>if you want to check for identity check the inode and device numbers (both) <joshuaBPMan>I'm considering trying to create guix packages for ikiwiki plugins. I'm guessing that I should use the perl-build system, but is there something special that I should do to make it an ikiwiki-plugin? maybe call the package ikiwiki-getfield ? <mbakke>joshuaBPMan: How does ikiwiki locate plugins at run-time? <mbakke>joshuaBPMan: If that is the case, I think perl-build-system will do the right thing. <joshuaBPMan>it mentions how to install 3rd party ikiwiki plugins. <joshuaBPMan>All plugins are in the IkiWiki::Plugin namespace, so they go in a IkiWiki/Plugin subdirectory inside the perl search path. <joshuaBPMan>For example, if your perl looks in /usr/local/lib/site_perl for modules, you can locally install ikiwiki plugins to /usr/local/lib/site_perl/IkiWiki/Plugin <mbakke>civodul: The reason I asked about trailing slash is because Guile-Gits 'repository-working-directory' includes a trailing slash, whereas the directory returned by canonicalize-path does not. I suppose I can string-drop the slash if libgit2 is truly consistent. <mbakke>joshuaBPMan: Sounds good. I think simply installing the plugin along with ikiwiki should work then. <mbakke>It could be that the ikiwiki service definition needs to be updated to take plugins however, since Guix services typically run with an empty environment. <joshuaBPMan>mkakke: I have a slight complication...it looks like the getfield is located at this website <joshuaBPMan>I'll go read the guix manual a bit and see if I can't figure it out. but it looks like most of the perl-packages use cpan... <joshuaBPMan>guix download is giving me a certificate error I have nss-certs installed...maybe I'm missing a certificate package.... <joshuaBPMan>I think I found the relevant guix documentation...no worries <mbakke>joshuaBPMan: You can probably package the ikiplugins repository with a custom phase that places it on the Perl search path. <jabranham>I asked on here a few weeks ago about guix finding an older guix version after guix pull in a new install on a VM. Someone helpfully provided a bash command that fixed it. I'm trying to report this as a bug properly now but can't remember the command. Does this ring a bell for anyone? <joshuaBPMan>mbakke: I'm not sure what you mean about packaging the ikiwiki repo.. <rekado>jabranham: you probably mean “hash” <joshuaBPMan>I've got an initial perl-getfield, but guix says guix build: error: #unspecified: not something we can package <rekado>“hash -r” forgets all remembered locations <rekado>joshuaBPMan: what command do you use? <rekado>joshuaBPMan: this sounds like you use -f with a file that doesn’t end with a package value. <joshuaBPMan>rekado: hmmm. let me check. I'm not sure what you mean, but I'll look <rekado>joshuaBPMan: how do you use that file that you pasted? <rekado>the file needs to evaluate to a package, but your file evaluates to #<unspecified>, because the last thing you do is defining a value. <civodul>mbakke: bah, maybe in that case you need to keep the canonicalize-path call <civodul>pkill9: what you experienced is the delay between the time something is built on berlin and the time it's available as a substitute <joshuaBPMan>rekado: I guess I'm not sure what change I need to make to have it define to a package <civodul>pkill9: substitutes are prepared upon the first request <joshuaBPMan>I don't see the differance between the hello package from the documentation than my local package *civodul wonders whether Conkeror is gone forever with IceCat 60 <roptat>joshuaBPMan: add "perl-getfield" at the end of the file? <joshuaBPMan>hmmm new error: No variable named perl in #<interface (gnu packages perl) 223ae60> <roptat>joshuaBPMan: I don't think you should define a module <roptat>you could replace these #:use-modules with (use-modules ...) <roptat>or even better use the guix repository (so it's easier for you to send a patch) <pkill9>civodul: i was told that berlin starts evaluating guix every time a commit is pushed to the guix repository <pkill9>oh i didn't read your first message <pkill9>so things aren't available as a substittute immediately after they're built <pkill9>what is the lag between something being built and it being available as a substitute? <civodul>pkill9: see the doc for 'guix publish --cache', basically it "bakes" the substitutes on the first request, and you were probably the first :-) <g_bor>I've contacted Holger, and told that I intend to participate on the r-b summit. <g_bor>rekado: I've seen the message you just sent. <rekado>g_bor: I’ll try to make room for the r-b summit. Haven’t decided yet. <g_bor>istm, that janneke and vagrant are willing to come. <rekado>g_bor: just FYI. Wanted to keep you up-to-date on applicants and people who might have been confused by the web interface. <g_bor>I've also seen civodul is thinking about having a meeting there a day before the summit <janneke>would be great if you could be there! <roptat>rekado: I can see "What is GNU Guix?" but not the project description *nckx relunctantly eats botsnack. <g_bor>I need some help, regarding the outreachy project description. <g_bor>In the text it says: Applicants can contribute to this project through the project repository or contribution page. <g_bor>Now I pointed the repository page to the savannah git repository, which seems ok, but there might be a better site to point to. <g_bor>I guess the repository listing on savannah would be a better place. <rekado>g_bor: I think the contribution page is the best pointer. <rekado>people might not know what to do with the savannah git repository listing. <g_bor>ok, looks much better now. I pointed to the contribution page. <g_bor>I've just fixed some bad links, and added further formatting and a few headlines to make the autogenerated text look good. <g_bor>rekado: I think we will need to get quite a lot of people involved int this project, especially if translations come into the picture <g_bor>In my opinion it would be great if we could easily add translations later, so that they do not become a blocker *g_bor trying to get kdenlive into shape... <g_bor>oops, looks like my updated patch to 30770 did not went to debbugs... trying to send it again... <roptat>g_bor: any update for the postgresql extension patch? <g_bor>roptat: not yet, but I would like to take a look at it. <g_bor>I was busy to get things in order for the Outreachy project. <jabranham>OK so I'm trying to start the sshd service. I added (service openssh-service-type) to services in the operating-system declaration. At the top, I have (use-modules <...> (gnu services networking)). But when I try to "sudo guix reconfigure /etc/config.scm" I get an openssh-service-type unbound variable error. Any pointers? <rekado>g_bor: the ffmpeg “Concat demuxer” could be used to generate the videos. <g_bor>I also thought to have a look at kdenlive, it is hanging on the patch queue for a while... <ngz>Hello. For some reason, I get "no code for module (gcrypt hash)" when using pre-inst-env script. I tried to do "guix environment guix" then "./configure --localstatedir=/var" and "make", to no avail. I pulled guix recently. <samplet>ngz: A quick stop-gap measure would be to use “guix environment guix --ad-hoc guile-gcrypt”. <samplet>It builds just fine, but then running “./pre-inst-env guix ...” fails? ***jonsger1 is now known as jonsger
<samplet>Well, that is strange, but running it from within an environment with “--ad-hoc guile-crypt” ought to help (even if it doesn’t really solve the root issue). <ngz>So I create the environment and use the script normally or do I try to build Guix ? <samplet>If Guix built okay, you can just us the script normally. <ngz>It seems to work. Thank you. <ngz>I can at least proceed with my monthly updates. <samplet>I seem to have guile-gcrypt in both my system profile and my user profile, so the pre-inst-env script works without an environment. (And I don’t have guix or guile-gcrypt explicitly installed.) <ngz>How do you check it is installed. <samplet>The “guix package -I” command lists all the currently installed packages (for the user profile). <ngz>You said that guile-gcrypt is not explicitly installed. How comes it appear in guix package -I? <samplet>It didn’t. It was in “~/.guix-profile/share/guile/site/2.2”, which was pointed to by GUILE_LOAD_PATH. <samplet>(Sorry, I could have been more clear!) <ngz>Guile-gcrypt doesn't seem to be there. <samplet>ngz: But GUILE_LOAD_PATH points to “~/.guix-profile/...”? <samplet>Are you on a foreign distro or using GuixSD? <samplet>Ah! You might need to do a bit of extra work setting up your environment. I think you can source “~/.guix-profile/etc/profile” to set up your profile’s environment. <samplet>However, you need to make sure that “~/.config/guix/current/bin” comes first in your path to make sure you are using the latest Guix. <ngz>I already source etc/profile, but PATH is set after that line. <ngz>Not my ".profile", no. <samplet>I mean “~/.guix-profile/etc/profile”. <samplet>Ah! I have it because of emacs-guix. I think it is not there by default, then, so you have to use the environment. <ngz>Or install emacs-guix, I guess. <rekado>g_bor[m]: I was hoping to avoid complicated GUI programs if possible. If regenerating the videos requires a series of complicated steps consisting of manual clicking around in a GUI that would make things difficult and tedious. <rekado>that’s what I’m worried about when proper video software would be used. <rekado>the most important work as I see it is in preparing the contents effectively so that they become understandable in the target medium. <rekado>the use of a full blown video editing could get in the way of that goal, I fear. <rekado>that’s just my opinion and there’s a good chance I could be wrong, of course. <rekado>I guess it depends on how repeatable the workflow would be.