IRC channel logs


back to list of logs

<jsierles>yup, that's what i've been doing
<jsierles>same result
<civodul>can you run wget for that URL from the same machine?
<jsierles>yes, it works
<jsierles>fwiw, this is my daemon invocation: "guix-daemon --build-users-group=guix-builder --disable-deduplication --max-jobs 20 --substitute-urls="
<civodul>and "guix download" also from that machine?
<jsierles>ERROR: X.509 certificate of '' could not be verified:
<civodul>next line?
<jsierles> invalid
<jsierles>a real error ,yay.
<civodul>hmm for substitutes we don't check certificates, so that's different
<jsierles>it's a letsencrypt cert
<jsierles>not sure if that matters
<civodul>"guix download --no-check-certificate" maybe?
<jsierles>that worked
<civodul>hmm hmm!
<civodul>does guix-daemon have (gnutls) in its GUILE_LOAD_PATH?
<civodul>i guess you'd notice if it didn't, but who knows
<jsierles>that variable is not defined
<jsierles>at least, not in the profile i'm in now
<civodul>i mean in /proc/N/environment, where N is the PID of guix-daemon
<civodul>that's a binary install right?
<jsierles>it's not in there either
<jsierles>yes, binary install
<civodul>right, so 'guix' augments GUILE_LOAD_PATH automatically
<jsierles>0.13.0. there's no GUILE_LOAD_PATH in proc unfortunately
<civodul>not a problem, as i wrote
<civodul>so you're sure the file in /var/guix/substitute/cache always comes back with (value #f)?
<civodul>specifically /var/guix/substitute/cache/*/ykpfif2wzabhnn0a88sw3f96paa33k2z
<jsierles>you dont think it's related to this cert error?
<civodul>i don't think so
<jsierles>yup, comes back like that every time
<jsierles>so the daemon is running the binary install version. not the 'current' guix i'm using for the client
<jsierles>does this matter?
<jsierles>dang, hoped the cert error would be relevant :)
<civodul>what about this command:
<jsierles>i dont get the cert error from hydra
<civodul>echo info /gnu/store/ykpfif2wzabhnn0a88sw3f96paa33k2z-r-minimal-3.4.0 | sudo _NIX_OPTIONS=substitute-urls= guix substitute --query
<civodul>so it works as expected; the file does *not* have (value #f) here
<jsierles>yeah. mysterious
<civodul>these things are rarely mysterious :-)
<civodul>now you know all the internal details anyway ;-)
<jsierles>i do, but still dont know whats wrong haha
<civodul>i don't know, it's hard to tell at this point
<civodul>ACTION off to bed
<jsierles>alright, have a good one
<jsierles>ok, do get the cert error for hydra after all.
<jsierles>civodul: for later, i found the issue was related to not running the substitute daemon with 'privileged' inside docker
<jsierles>eh, nevermind
<jsierles>it worked for 'no-grafts' this time. but without that, the nar file is empty
<user_trisquel>Is GuixSD a GNU package?
<user_trisquel>Is it the only true OS in Church of Emacs?
<bavier>took me 4 days but I finally got my netbook's packages upgraded
<oriansj>sneek: later tell bms_ that the discussion about stage0 have moved to #bootstrappable
<sneek>Got it.
<oriansj>sneek: botsnack
<rfmj>Whats means * on (file-systems (cons* ?
<rekado_>rfmj: “cons” only takes one atom and a base list. “cons*” can take more than one atom and a base list.
<rfmj>ok. i imagined "cons *" means bootable. thanks
<rfmj>supposed i have make a /boot partition, on "config.scm", file-systems list need "/boot" on first place before "my-root", "home"...? how i make /boot partition bootable?
<rekado_>rfmj: you have to make partitions bootable the usual way: with something like cfdisk
<rfmj>thanks rekado_ :) more one question: the (file-systems (cons... "home", "boot", order make difference?
<rekado_>I don’t think it makes a difference, but I must admit that I’m not 100% sure.
<rfmj>ok, i will try my first install on qemu, thanks a lot, rekado_ :)
<rekado_>rfmj: when using qemu note that you cannot use “ping” to test network connectivity.
<rekado_>it’s a common source of confusion
<rfmj>ok :)
***enick_890 is now known as sturm
<jsierles>hey guix
<jsierles>in the output of 'guix substitute --query', anyone know what the last two numbers are for?
<jsierles>I'd like to modify the guixsd 0.13.0 VM boot image to add a console to the kernel arguments for Google Compute Engine. would the best way be to boot it locally, reconfigure, then save the vm?
<rekado_>jsierles: I think you can just build a new VM image with a configuration that includes the console arguments to the kernel.
<jsierles>rekado_: i see. how do you create a VM image?
<jsierles>ah, i see 'guix system' has a way
<jsierles>will give that a try. i suppose there I can also configure ssh and such
<user_trisquel>So is Guix the only true OS in GNU?
<jsierles>i want to add a service that also fetches google cloud metadata to be used for configuring the system at boot time
<rekado_>user_trisquel: no.
<user_trisquel>rekado_: And is GuixSD a GNU package?
<rekado_>user_trisquel: Guix is a GNU package. GuixSD is a “manifestation” of Guix.
<user_trisquel>rekado_: Can system distribution be GNU package?
<jsierles>i wonder if anyone looked into packaging docker. getting it working on guixsd would be a big win I think
<jsierles>i'm confused about the difference between /var/guix/profiles/default and /var/guix/profiles/per-user
<jsierles>i currently have ~/.guix-profile linked to /var/guix/profiles/per-user/root/guix-profile. if i run 'guix package -i r-minimal' it creates a link in /var/guix/profile/default
<jsierles>do i have to manually change the link in my directory from 'per-user' to 'default'?
<rekado_>I don’t even have “/var/guix/profile/default” on my machines.
<jsierles>rekado_: ok. does that mean if i remove it, 'guix package' will update links per-user instead?
<jsierles>in my case, everything always runs as root (inside docker) so there's never more than one user
<rekado_>even when I run “guix package” as root it creates /var/guix/profiles/per-user/root/
<rekado_>I don’t know why you ended up with “default”
<rekado_>or how
<jsierles>default comes with the 0.13 binary installation
<jsierles>actually, even if i delete the defaults dir, it gets recreated by guix
<rekado_>ah, it’s from (guix scripts package)
<rekado_>it checks for "USER" and "LOGNAME".
<rekado_>if neither of these are set it goes to “default”
<rekado_>yet another side-effect of running this inside Docker, I guess.
<jsierles>I see, good to know
<jsierles>rekado_: do you know which file i can look at to work out what the numbers in the output of 'guix substitute --query' mean?
<rekado_>“buffered” and “timeout” maybe?
<rekado_>what numbers are these for example?
<rekado_>oh, in the *output*
<rekado_>it just reads the acl file, no?
<jsierles>rekado_: there are two numbers at the end of the output
<jsierles>at the end you can see '0' and '40934552'
<jsierles>hydra reports a different number than '0' for various queries. my server always reports '0'
<jsierles>just trying to figure out what's busted with my sub server.
<rekado_>I think that’s handled by (guix scripts substitute)
<rekado_>the “info” query results in display-narinfo-data to be called
<rekado_>and that prints two numbers at the end
<rekado_>(or (narinfo-file-size narinfo) 0)
<rekado_>and (or (narinfo-size narinfo) 0)
<jsierles>ok. so it's reporting the file size as zero, maybe that's the root issue
<jsierles>so 'narinfo' must be empty in the first place
<jsierles>where are these narinfo files actually stored?
<rekado_>have you inspected/deleted your local substitute cache already?
<jsierles>rekado_: yes, done that multiple times, easy to reproduce
<rekado_>you need to read the code yourself: lookup-narinfos/diverse fetches narinfos if they are not cached.
<jsierles>the cache for the package in question contains #f. civodul said that means the server is not returning a narinfo
<jsierles>it does return one, but with that 0 filesize
<jsierles>i know where they are stored locally - i meant on the substitute server.
<rekado_>the substitute server prepares them on demand, dependent on settings. It’s documented in the manual for guix publish.
<rekado_>ACTION needs to get back to debugging this texlive problem
<jsierles>right - so no way to inspect them
<jsierles>i guess turning on the cache then could help debugging
<jsierles>thanks, sorry to bug you
<ng0>how do I escape dots? \\\\\\. or \\\\. ? \\. did not work
<jsierles>rekado_: how do you deal with 'guix gc' on a shared cluster?
<jsierles>the docs suggest that 'guix gc' determines what to delete by only keeping packages used by profiles.
<jsierles>so that means all profiles in /var/profiles have to be visible to the daemon, right? including those generated by users on other machines.
<davexunit>rekado_: #fsf is SO very frustrating
<jsierles>correct me if i'm wrong, but having access to the 'guix gc' command means you can delete anything in a store, including things that others might be using
<quiliro>i am finally able to connect again
<rekado_>jsierles: no
<rekado_>jsierles: you cannot delete what’s in use
<jsierles>'in use' is defined as 'belonging to a profile'?
<rekado_>there are garbage collector roots
<quiliro>rekado_: in the qcintilla web page it says how to build python bindings
<quiliro>would you guide me how to do it?
<rekado_>jsierles: take a look at /var/guix/gcroots/
<rekado_>quiliro: sure
<jsierles>"The set of garbage collector roots includes default user profiles"
<rekado_>quiliro: I think this should be a separate package
<adfeno>davexunit: rekado_: About some people at #fsf frustrating us: Agree :)
<efraim>ng0: \\\\. , the first for guile and the second to actually escape the dot
<ng0>ok, thanks
<quiliro>rekado_: wait...that is not where i read it...i think it was in README.html
<quiliro>on the source code
<quiliro>let me check
<jsierles>rekado_: so, it just looks at user profiles. do you also mount /var/guix/profiles over NFS?
<rekado_>the state directory must be available
<jsierles>rekado_: OK, so it's writeable, and you don't have to login to the build server to manage profiles?
<rekado_>the profiles directory is writeable on all nodes, and UIDs are centrally managed.
<rekado_>but the remote Guix instances must talk to the central daemon.
<jsierles>i see. i guess they key then is UIDs, so people cant overwrite each others profiles
<rekado_>it’s just the link manipulation that’s performed directly.
<rekado_>yeah, you don’t want to share a writeable directory over NFSv3 (NFSv4 has uid mapping) with machines whose uids cannot be controlled
<jsierles>yeah, OK that makes sense. so I'd have to deal with the perms/UID problem mainly
<jsierles>i'll be using nfsv4 (via glusterfs)
<quiliro>rekado_: is in QScintilla_gpl-2.10.1/doc/html-Qt4Qt5/index.html
<quiliro>rekado_: The configure, build and install the bindings for PyQt v4, run: python
<quiliro> make
<quiliro> make install
<quiliro>If you want to build the bindings for PyQt v5 then pass –pyqt=PyQt5 as an argument to
<jsierles>rekado_: so the guix client needs to be able to see /var/guix/*, or just /var/guix/profiles/per-user/mydir?
<quiliro>rekado_: QScintilla includes an optional plugin for Qt Designer that allows QScintilla instances to be included in GUI designs just like any other Qt widget.
<rekado_>quiliro: so we need a new package expression called “python-qscintilla” that has “qscintilla” and “python” as inputs
<quiliro>rekado_: i dont know if this Qt Designer plugin will be necessary
<rekado_>quiliro: no
<quiliro>rekado_: ok...shall i put “python-qscintilla” on qt.scm after "qscintilla"?
<rekado_>quiliro: you can use the gnu-build-system and replace the “configure” phase with a procedure (lambda) that runs “python --pyqt=PyQt5”
<rekado_>quiliro: yes.
<rekado_>quiliro: also add python-pyqt to the inputs.
<quiliro>rekado_: ok...any other thing to put it in?
<rekado_>normally, we would use the python-build-system for Python things, but in this case the behaviour is closer to the gnu-build-system.
<rekado_>quiliro: I guess we’ll see when we get the first build errors.
<quiliro>rekado_: how can i know that...i know you do, but i want to learn too
<rekado_>quiliro: about the build system?
<quiliro>i ask this about: "normally, we would use the python-build-system for Python things,
<quiliro><rekado_> quiliro: I guess we’ll see when we get the first build errors.
<quiliro><quiliro> rekado_: how can i know that...i know you do, but i want to learn
<rekado_>quiliro: the GNU build system is used by many applications
<rekado_>it requires that a user runs “./configure”, then “make” and then “make install”.
<ng0>Does (gnu packages zip) no longer exist?
<ng0>It seems so to me
<adfeno>ng0: Gone to gnu packages compression
<rekado_>ng0: yes
<rekado_>quiliro: In Guix we have an abstraction for this: gnu-build-system.
<rekado_>quiliro: for Python software a user needs to run “python install” (or similar)
<ng0>ok, that explains one mistake
<ng0>but it still loads from the .go
<rekado_>ng0: delete it
<quiliro>rekado_: thank you...i will now proceeed to create python-qscintilla
<rekado_>quiliro: and that’s abstracted in python-build-system
<quiliro> python
<quiliro> make
<quiliro> make instal
<quiliro>so it does include python
<adfeno>quiliro: "Build systems" in Guix are like a predefined set of order. In real life, I would train my dog (if I had one) to "sit" (order) by influencing him to do a series of detailed steps to do so.
<rekado_>the gnu-build-system has a couple of phases (you might remember them from last time)
<rekado_>such as: unpack, configure, build, install, …
<rekado_>none of these phases runs “python”
<rekado_>so we need to add it
<rekado_>the “configure” phase of the gnu-build-system tries to run a “configure” script.
<quiliro>and pass –pyqt=PyQt5 as an argument to
<rekado_>we don’t have that, so we can just replace that phase.
<quiliro>let me get to chew this over and make the changes to qt.scm
<quiliro>rekado_: it does not need to download what do i use for version and source
<rekado_>you can inherit from qscintilla
<rekado_>after all, these two packages should be in sync
<quiliro>how to do that?
<rekado_>(define-public python-qscintilla (package (inherit qscintilla) …))
<rekado_>you can then leave off the “version” and “source” fields
<quiliro>rekado_: “qscintilla” and “python” "python-pyqt" as inputs?
<quiliro>those 3?
<rekado_>but then do “python3”, not “python”
<quiliro>or qscintilla is not needed because it it already in the inherits
<rekado_>it’s needed
<rekado_>inherit just inherits fields
<rekado_>it does not add a package to the inputs that wasn’t previously among the inputs.
<quiliro>(inputs `((“qscintilla” ,qscintilla)
<quiliro> (“python” ,python)
<quiliro> ("python-pyqt" ,pyhton-pyqt))
<rekado_>quiliro: check your spelling and your quotes
<quiliro>i see the spelling error...but where is the quote error?
<quiliro> `(#:phases
<quiliro> (modify-phases %standard-phases
<quiliro> (replace 'configure
<quiliro> (lambda* (“python3 --pyqt=PyQt5”))))))
<rekado_>you use “ but you should use "
<quiliro>i dont know how to use that
<quiliro>i only have "
<rekado_>and that’s the one you should use :)
<ng0>you could also do something like (inputs `(("yournewthing" ,yournewthing) ,@(package-inputs packagename-you-inherited-from)))
<rekado_>looks like you copied these quotes
<rekado_>ng0: that’s not needed here
<adfeno>rekado_: Actually, what ng0 suggested could work :)
<rekado_>it’s better not to create too many dependencies
<quiliro>is the arguments part correct?
<rekado_>these packages might change and that would change the inputs to the Python bindings
<rekado_>we don’t want that
<quiliro>ive corrected the “
<rekado_>remember how we run commands with Scheme?
<quiliro>how should they be?
<ng0>I don't know the package or context, so I guess yo uare right
<rekado_>quiliro: you did the right thing before with qscintilla
<adfeno>lambda _ ... zero? system* :)
<quiliro>in qscintilla:(arguments
<quiliro> `(#:phases
<quiliro> (modify-phases %standard-phases
<quiliro> (replace 'configure
<quiliro> (lambda* (#:key outputs #:allow-other-keys)
<quiliro>maybe in medical.scm (openmolar)
<quiliro>no. there it is: (lambda* (#:key outputs #:allow-other-keys)
<quiliro>i remember we had zero system...but i cannot find it now
<adfeno>quiliro: Try git diff...
<adfeno>It might show you which files do have the zero system sequence
<rekado_>ACTION has to go
<quiliro>git diff
<quiliro>did those paste come with the correct information?
<quiliro>qscintilla is in qt.scm
<ng0>I'll send a patch for this now and hope an existing patch will let someone fix it so that I can drop my local, correct variant.
<joshuaBPMan_>Does anyone else have a problem with their mouse not clicking on things? ie: you click on the "File" in Firefox or any other application, and the file menu doesn't open? I can't even open a new tab via clicking on it in Firefox. I have to press C-t...
<quiliro>joshuaBPMan_: first test: replace the mouse
<joshuaBPMan_>quiliro: the mouse works fine on my parabola machine, but i do have another mouse lying around...
<quiliro>joshuaBPMan_: second test: test other buttons (including pressing the mouse wheel)
<quiliro>joshuaBPMan_: same mouse works in different system...test #2
<joshuaBPMan_>quiliro: The 2nd mouse had the same issues. And pressing all the mouse buttons had no effect in firefox.
<joshuaBPMan_>But the mouse wheel did work in the terminal.
<quiliro>joshuaBPMan_: on the terminal can you select text with the left mouse button?
<quiliro>7out of battery...bye
<joshuaBPMan_>8 packages in profile
<joshuaBPMan_>but I had to press alt-E to copy the text.
<jsierles>i got this: profile contains conflicting entries for linux-libre-headers:out
<jsierles>this is propagated from glibc@2.25
<quiliro>i could come back...did you read my pastes?
<quiliro>joshuaBPMan_: so your mouse button works
<quiliro>rekado_: will you continue to guide me?
<quiliro>or anyone else would like to help guide me to create python-qscintilla package?
<quiliro>this is my take at the moment on qscintilla:
<quiliro>i did not understand where zero? (system* .... would go
<quiliro>adfeno: what do you think?
<quiliro>hello janneke
<janneke>hi quiliro
<quiliro>janneke: what are you up to with guix?
<janneke>in the evenings i work on Mes: guix's bootstrap path
<janneke>during the day i am introducing guix as a ubuntu replacement for a client
<quiliro>janneke: cool!
<quiliro>janneke: does Mes have documentation?
<janneke>quiliro: thanks! Mes has the usual READMEs and there's the slides of my fosdem talk giving a high level overview -- nothing close to the code yet
<janneke>quiliro: what kind of documentation would you be looking for?
<ng0>quiliro: in a new phase
<ng0>Assuming that you have a local checkout of guix.git, use: egrep -nr "system*" gnu/packages in the root of it to find examples
<ng0>there are lots of them in python.scm
<quiliro>janneke: just wanted to know what Mes would be nice to see a video or listen to an audio of your presentation
<quiliro>ng0: why do i need that?
<quiliro>ng0: did you see the link to my paste?
<ng0>I'm not sure, I wasn't following your thing
<ng0>you asked for the reason for system etc
<ng0>eh for the location
<ng0>I can't really open a webbrowser at the moment
<ng0>I'm compiling a webbrowser, which is taking up resources because offloading decided to not work
<quiliro>ng0: wget?
<quiliro>it is just text of the diff
<quiliro>maxwell equations of software!
<quiliro>i get bad gateway on
<quiliro>am i the only one?
<quiliro>janneke: i did not see your link on the guix talks page
<CharlieBrown>Guix's RetroArch won't load Mupen64+ core.
<quiliro>would anyone care to view my diff at qscintilla:
<mekeor>quiliro: in the URI-field, you append the version to the string "". but this string already contains the version. maybe you could instead use something like (string-append "" version "/QScintilla_gpl-" version ".tar.gz") ? :) – otherwise, looks good to me :)
<quiliro>mekeor: very smart! thank you
<quiliro>what i am doing now is you think it is correct?
<quiliro>check out the new diff
<quiliro>mekeor: corrected qscintilla. now, what do you think about my python-qscintilla?
<quiliro>adfeno: inlcuded zero? (system* ..... please check it out
<quiliro>rekado: good you are back....please check my progress:
<quiliro>rekado: on python-qscintilla
<mekeor>quiliro: the description-field is a very long string. it should be written on multiple lines instead of a single line. – other then that, looks good to me
<quiliro>mekeor: python-qscintilla has no description field
<quiliro>how long should description lines be?
<mekeor>quiliro: i was talking about qscintilla, ofc
<quiliro>mekeor: no space before linefeed?
<mekeor>quiliro: i don't know. i think about 80 characters. also i don't know about space before linefeed. maybe you could just compare to other package definitions?
<quiliro>mekeor: yes! thank you
<rekado>quiliro: I’m still on the way with poor internet connection. [20:06]
<rekado><rekado> quiliro: I remember fixing qscintilla, including the description and the url.
<rekado>quiliro: when in Emacs, put point onto the description string and hit M-q
<rekado>this will reflow the paragraph
<quiliro>great to know, rekado
<quiliro>my last changes:
<rekado>your lambda looks weird
<rekado>why do you write (“python3 --pyqt=PyQt5”) ?
<rekado>that’s not going to do anything but throw an error.
<quiliro>what is the correct synthax?
<rekado>try this in the REPL
<rekado>well, we need to call a system command, right?
<rekado>this means we should use “system*” at the beginning of the expression
<rekado>(system* "ls")
<rekado>ACTION needs to go offline for 20 mins
<quiliro>rekado: i dont remember how to start the REPL
<rekado>you need to take notes :)
<rekado>C-c C-z from a Scheme buffer
<quiliro>i was C-s REPL
<mekeor>... or type "guile" in a console/terminal
<quiliro>but found none
<quiliro>looked for guile too...i wonder if my log is not complete
<rekado>in the REPL you can also access documentation
<rekado>type system* and then hit C-c C-d C-d
<quiliro>oh! cool
<quiliro>rekado: did (system* "ls")
<quiliro>in guile
<quiliro>what about '(“python3 --pyqt=PyQt5”)'?
<quiliro><rekado_> but then do “python3”, not “python”
<quiliro><rekado_> quiliro: you can use the gnu-build-system and replace the
<quiliro>first comment was after the others
<mekeor>quiliro: i think the point is that you need system*
<quiliro>system is not included?
<jonsger>ERROR: X.509 certificate of '' could not be verified:
<jonsger> signer-not-found
<jonsger> invalid
<jonsger>what do I have to do/install?
<mekeor>quiliro: the `system*` function is missing in your package definition of python-qscintilla inside the `lambda*` inside `replace` inside `modify-phases` ...
<mekeor>jonsger: what was the command which lead to the error?
<jonsger>mekeor: guix download
<rekado>jonsger: do you have nss-certs installed?
<jonsger>rekado: yes
<rekado>jonsger: if so, did you set up the SSL_* environment variables?
<rekado>jonsger: take a look at the X.509 certificates section of the manual
<jonsger>yeah. I found it. thx
<rekado>quiliro: you cannot just put a string in parentheses and expect that it will be executed as a shell command.
<rekado>quiliro: you have to use system* for that.
<quiliro>(zero? (system*
<quiliro> "./configure"))
<rekado>that would run an executable “configure”
<rekado>and check its return value
<rekado>but that’s not what the installation instructions said we should do
<joshuaBPMan_>how does guix environment guix create the best environment for hacking on guix?
<joshuaBPMan_>does it create a git repo somehow?
<rekado>joshuaBPMan_: no, you need to bring the repo yourself
<rekado>it just sets up a sub-shell where all tools you will need to build Guix are available
<joshuaBPMan_>hmmm. Ok. When I read the contributing section it seemed to say that guix environment guix was enough to get started. thanks rekado
<rekado>maybe this could be clarified.
<rekado>we’re assuming that people will have a copy of the sources.
<quiliro>rekado: the instructions say python --pyqt=PyQt5 ... make ...make install
<quiliro>i dont understand how this becomes in guile
<rekado>these are three separate commands
<quiliro>my latest diff
<rekado>the latter two are already taken care of by gnu-build-system
<rekado>“make” is run during the “build” phase
<rekado>“make install” is run during the “install” phase.
<rekado>so we just need to call “python” (or rather “python3”) with a couple of arguments
<rekado>when you want to call “ls” you would do (system* "ls")
<rekado>if you wanted to call “ls -l /tmp” you would do (system* "ls" "-l" "/tmp")
<rekado>what do you think needs to be done to call the python command?
<quiliro>system* "python3" "" "5
<quiliro><rekado> correct
<quiliro><quiliro> i dont understand how this becomes in guile [13:41]
<quiliro><rekado> these are three separate commands
<quiliro><quiliro> my latest diff
<quiliro><rekado> the latter two are already taken care of by gnu-build-system
<quiliro><quiliro> yes
<quiliro><rekado> “make” is run during the “build” phase
<quiliro><quiliro> yes [13:42]
<quiliro><rekado> “make install” is run during the “install” phase.
<quiliro><quiliro> yes
<quiliro>sorrry sorry sorry
<rekado>careful with pastes :)
<quiliro>i dont even know why that happenned...i just hit enter
<quiliro>(system* "python3" "" "--pyqt=PyQt5")
<rekado>wrap this in “zero?” to check for errors
<rekado>I guess one more thing is missing.
<rekado>Before you run this command you need to enter the directory containing “”.
<rekado>you already know how to do this (see qscintilla)
<quiliro>(zero? (system** "python3" "" "--pyqt=PyQt5"))
<rekado>when you’re ready you can try building it and see how far you get
<quiliro>how about the lambda part?
<quiliro>(lambda* (#:key outputs #:allow-other-keys)
<quiliro>is that correct for this case?
<rekado>it’s a bit too much
<rekado>we don’t care about the “outputs” in this phase
<rekado>you can replace it with the “don’t care” variant: (lambda _ …)
<quiliro>(lambda _ (chdir "Qt4Qt5") (zero? (system** "python3" "" "--pyqt=PyQt5")))
<rekado>I think the directory name is different
<rekado>also, it’s “system*” not “system**”
<quiliro>where do i find the directory name?
<rekado>quiliro: look at the sources / the installation instructions
<quiliro>it says nothing there about changing directory on python bindings...only on qscintilla
<rekado>in that case just give it a try withouth the chdir
<rekado>I thought the python stuff is in a sub-directory
<quiliro>The configure, build and install the bindings for PyQt v4, run: python
<quiliro> make
<quiliro> make install
<quiliro>ok, i can comment that part out
<quiliro>(lambda _ (zero? (system** "python3" "" --pyqt=PyQt5"))
<quiliro>missing a closing )
<rekado>if you’re using paredit you’ll rarely ever have mismatched parentheses
<quiliro> is tha last modification
<quiliro>rekado: this was one of those rare happenings, haha
<quiliro>what do you think?
<quiliro>about the paste
<rekado>have you tried it yet?
<quiliro>./pre-inst-env guix environment --ad-hoc python-wrapper python-pyqt qscintilla
<rekado>there are still a couple of things I’d change (and have changed before). Do you still have my previous version of qscintilla?
<quiliro>wrong yank
<rekado>./pre-inst-env guix build python-qscintilla
<quiliro>that is what i meant
<ng0>should I wait until Arun has send mksh or should I send oksh and the person applying the patch just rebases?
<quiliro>guix build: warning: failed to load '(gnu packages kodi)':
<quiliro>ERROR: In procedure module-lookup: Unbound variable: libdvdnav
<rekado>quiliro: there’s an error higher up. Look for the first error.
<quiliro>guix build: warning: failed to load '(gnu packages bioinformatics)':
<quiliro>ERROR: In procedure module-lookup: Unbound variable: perl-libwww
<quiliro>/home/quiliro/guix/gnu/packages/qt.scm:1427:2: warning: extraneous field initializers (inherit)
<quiliro>that is the oldest
<quiliro> (inherit "qscintilla")
<ng0>I'll just send
<ng0>easier to just do it than asking
<quiliro>i see it correct
<rekado>quiliro: two things: the inherit should be right after “package”
<rekado>and second: you cannot inherit from a string.
<rekado>you have to inherit from a package variable —> qscintilla
<quiliro>no "
<quiliro>doing its work now
<quiliro>error again
<rekado>where’s the error?
<quiliro>guix build: error: /home/quiliro/guix/gnu/packages/qt.scm:1427:2: package `python-qscintilla-2.10.1' has an invalid input: (#{\\x201c;qscintilla\\x201d;}# #<package qscintilla@2.10.1 /home/quiliro/guix/gnu/packages/qt.scm:1378 25623c0>)
<quiliro>latest diff
<rekado>check your quotes
<quiliro>all " are paired
<quiliro>inputs use “
<rekado>that’s wrong
<rekado>don’t use “
<quiliro>pre-inst... is running
<quiliro>python3: can't open file '': [Errno 2] No such file or directory
<rekado>so you need to check the qscintilla source code and look for it.
<rekado>get the sources with ‘guix build -S’, unpack it, and then search for the file
<ng0>should we maybe point out in the documentation that you must use " ? I thought it was obvious, but " is the type I learned on the typewriter to use many years ago
<rekado>I don’t think this belongs into Guix documentation.
<rekado>and I’m pretty sure that the Guile documentation mentions that " is the only character to be used for strings.
<ng0>is it just me, do I need to run make clean again or does someone else get "ERROR: No variable named %final-inputs in #<directory (gnu packages commencement) 326fd20>" at HEAD?
<quiliro>it is Python directory
<quiliro>(chdir "Pyhton")
<ng0>okay, it is just me. I moved this package from my local overlay to the guix master without fixing the license:
<quiliro>new diff
<quiliro>is that correct?
<quiliro>rekado: ^
<rekado>you forgot the quotes
<rekado>(chdir Python) with changed to the directory specified in the variable ‘Python’
<quiliro>(chdir "Python")
<rekado>try this first before sending another paste
<quiliro>doing it
<quiliro>slow machine
<quiliro>starting phase `configure'
<quiliro>In ice-9/boot-9.scm:
<quiliro> 160: 15 [catch #t #<catch-closure 8c5dc0> ...]
<quiliro>In unknown file:
<quiliro> ?: 7 [primitive-load "/gnu/store/dqxb20kbdf9p10988yqiy3qvndca2zn5-python-qscintilla-2.10.1-guile-builder"]
<quiliro>ERROR: Unbound variable: Python
<quiliro>should i create a paste?
<rekado>that looks like the same error
<rekado>you’re using Python as a variable, not as a string
<rekado>did you actually save your changes?
<quiliro>i did it again , in case i didnt
<quiliro>running again
<quiliro>different error
<quiliro>Error: Qsci/qsciglobal.h could not be found in
<quiliro>/gnu/store/6wmrf9c7rpv2c8q02vxvv1frsmljr5lh-qtbase-5.9.1/include. If QScintilla
<quiliro>is installed then use the --qsci-incdir argument to explicitly specify the
<quiliro>correct directory.
<rekado>(system* "python3" "" "--pyqt=PyQt5" (string-append "--qsci-incdir" (assoc-ref inputs "qscintilla") "/include"))
<rekado>but you’ll need to change the “don’t care” lambda to (lambda* (#:key inputs #:allow-other-keys) …)
<rekado>(system* "python3" "" "--pyqt=PyQt5" (string-append "--qsci-incdir=" (assoc-ref inputs "qscintilla") "/include"))
<quiliro> lambda*: invalid argument list in subform ("Python") of (chdir "Python")
<quiliro>this is the latest qt.scm
<rekado>check your parentheses
<rekado>you’re missing a big chunk of the lambda
<rekado>(#:key inputs #:allow-other-keys)
<rekado>please be more careful to avoid these delays
<joshuaBPMan_>well I believe I've just installed guix via git.
<quiliro>rekado: i dont see the error
<quiliro>inputs or outputs?
<rekado>I wrote “lambda”
<quiliro>(#:key outputs #:allow-other-keys)
<quiliro>i checked and i dont see missed parenthesis
<rekado>you’re looking at the wrong package definition
<quiliro> (lambda* (#:key inputs #:allow-other-keys)
<quiliro>runining pre-inst....
<quiliro>Usage: python [options]
<quiliro> error: '' is not a directory
<quiliro>will check
<quiliro>this is the latest python-qscintilla and qscintilla
<quiliro>Error: Qsci/qsciglobal.h could not be found in
<quiliro>that is a past error...not on this run
<quiliro>Usage: python [options]
<quiliro> error: '' is not a directory
<quiliro>is in this run
<quiliro>ice-9/psyntax.scm:1796:40: In procedure #<procedure 9aa300 (args e1 e2 args* e1* e2*)>:
<quiliro>ice-9/psyntax.scm:1796:40: Syntax error:
<quiliro>/gnu/store/hvrbqkyzwrg8s83kbklgk9kmp7q8vdwn-python-qscintilla-2.10.1-guile-builder:2:566: lambda*: invalid argument list in subform ("Python") of (chdir "Python")
<quiliro>it is saved
<quiliro>that was before the last pre-inst...
<quiliro>backed up too much
<quiliro>it cannot find some directory because it is blank
<rekado>quiliro: please be more careful to double check that you’ve written the right thing
<rekado>what you wrote is not what I suggested
<rekado>I need to concentrate on other things now
<rekado>please take your time in trying to understand what you’re doing and what the errors mean
<quiliro>i did not know i had to include that part of lambda
<quiliro>rekado: please tell me how to investigate and what to read
<rekado>quiliro: for example, you could re-read the log and my suggestions and then compare them with what you’ve written.
<rekado>quiliro: also play with these things in the REPL
<reepca>Hm, why do we have headers in subdirectories? For example, ~/.guix-profile/include/mono-2.0/mono/*.h instead of ~/.guix-profile/include/mono/*.h. Seems like you'd need to add every one of those subdirectories to C_INCLUDE_PATH or something similar in order for existing #includes to work.
<rekado>that tripped me up, too
<rekado>I’m currently packaging sooperlooper and it can’t find a couple of things because of that
<rekado>we have them because that’s how upstream decided to install things
<rekado>we don’t usually override upstream decisions like that.
<LuNaTicPanDora>Newbie here trying to get GuixSD up and running. I'm being prompted for some login credentials but can't find any information in the documentation. Can anyone help with this?
<rekado>LuNaTicPanDora: at what point are you prompted?
<LuNaTicPanDora>Just after the system has booted and the tty prompts are listed.
<ng0>LuNaTicPanDora: the root password is empty. you need to manually (passwd) set a passowrd for non-root users
<ng0>or is this still before the system is installed?
<LuNaTicPanDora>Is there a username that I'm meant to enter?
<LuNaTicPanDora>I'm using the VM image from the ftp site
<ng0>are you in the installer medium? Or did you already boot into the generated system?
<LuNaTicPanDora>Booted into a generated system.
<ng0>oh.. I never touched this. No idea. My guess is "root" with empty password.
<ng0>someone else will know
<LuNaTicPanDora>yep root worked
<LuNaTicPanDora>thanks for the suggestion ng0
<quiliro>i pasted the whole python-qscintilla definition
<quiliro>in the REPL
<quiliro>got a lot of possibly unbound variable:
<quiliro>package, inherit, qscintilla,name, etc
<quiliro>i understand that is because i have not entered those before python-qscintilla
<quiliro>but i dont understand how to test python-qscintilla in the REPL
<quiliro>i will read the REPL MANUAL
<rekado>when I suggested to play in the REPL I didn’t mean pasting the whole definition there
<rekado>to interact with the whole definition is possible, but less instructive
<rekado>just take small parts like (string-append…) and see what they do to learn how they should be called
<quiliro>thank you
<quiliro>i found a parenthesis in the wrong place
<quiliro>useful this REPL praactice
<adfeno>quiliro: I also use this practice too :)
<ng0>Is someone interested in the public domain OpenBSD 'mg' editor? I packaged this today in one of my repositories and could simply upstream it.
<civodul>rekado, lfam: FYI i'll be AFK until Monday
<civodul>hi! BTW :-)
<lfam>civodul: Okay, I'll be working on core-updates
<civodul>lfam: i'm building my system on it right now
<civodul>seems to be doing ok :-)
<civodul>well, it's "building stuff"
<civodul>i have a fixlet for the ath9k firmware
<lfam>I have almost reconfigured my non-graphical x86_64-linux system based on it, but a patch for something in the ath9k drivers graph doesn't apply
<lfam>Oh, good :)
<lfam>I was about to ask, "Does anyone want to investigate ath9k?" :)
<lfam>I'm going to push an update for wayland-protocols, too. It's not really that low in the package tree
<lfam>I restarted the build on glib for x86_64-linux on Hydra yesterday but it's still queued :/
<quiliro>Error: The QScintilla library could not be found in
<quiliro>/gnu/store/6wmrf9c7rpv2c8q02vxvv1frsmljr5lh-qtbase-5.9.1/lib. If QScintilla is
<quiliro>installed then use the --qsci-libdir argument to explicitly specify the correct
<quiliro>ithat is the error i had after checking synthax.....i am sorry for the mistake, i will be more respectful of your time...
<quiliro>i suppose that another string append has to be included
<quiliro>regarding --qsci-libdir
<quiliro>is that correct?
<quiliro>civodul: ni vidos vin lundo, gis!
<quiliro>(string-append "--qsci-libdir=" (assoc-ref inputs "qscintilla") "/include")
<quiliro>is this correct?
<quiliro>after (string-append "--qsci-incdir=" (assoc-ref inputs "qscintilla") "/include")
<adfeno>quiliro: Probably that's correct, let's test it :)
<quiliro>have an error...let me check the synthax
<quiliro>in fact it was parenthesis error
<quiliro>paren helps but not if the parenthesis are in the wrong places if they are paired
<quiliro>Error: The QScintilla library could not be found in
<quiliro>/gnu/store/9a21dnhx7paa1nbgs9w0yahb30jfdmni-qscintilla-2.10.1/include. If
<quiliro>QScintilla is installed then use the --qsci-libdir argument to explicitly
<quiliro>specify the correct directory.
<adfeno>I wonder which build is failing first...
<adfeno>I mean: builds in guix have an "order", this is why we sometimes see lots of "failed to build" from Guix...
<adfeno>The first one that has a message from Guix itself, is the one that we should be chaning :)
<quiliro>that is the first error
<quiliro>triple checked
<quiliro>so i dont make people waste time
<adfeno>quiliro: But from which package? I assume it's python-qscintilla, but I'm asking just to make sure.
<reepca>the FFI in our gforth is a bit broken - it should have libtool, libltdl, and libffi as inputs. Or at least, adding some subset of those seems to have fixed it.