<espectalll[m]>I'll be straight on this one: what does the error `no code for module` mean, when trying to build a package script? <espectalll[m]>If the error is too generic, no problem – I can actually send my current `.scm` <OrangeShark>espectalll[m]: sounds like you might of misspelled a module name <OrangeShark>did you set the path or use the option to add a path? <espectalll[m]>then added `rust-ansi-term.scm` (that's the package) at the root of such directory <OrangeShark>so the scm file should be at the root of the directory specified in GUIX_PACKAGE_PATH <OrangeShark>so if you have ~/guix-packages then it should be ~/guix-packages/rust-ansi-term.scm <espectalll[m]>I just noticed the error appears no matter the Guix command I use <OrangeShark>espectalll[m]: oh, you need to use guile define-module <OrangeShark>so your module would be called (define-module (rust-ansi-term) #:use-module ...) <OrangeShark>it is fine, I was confused at how guile modules worked at first too. <OrangeShark>one thing that confused me was that it uses the path as part of the module name so if you want a module (foo bar baz) you would want to create a file at the root directory as foo/bar/baz.scm <espectalll[m]>When I discovered it at first it was indeed confusing – also felt verbose <OrangeShark>that means you put the file in gnu/packages/rust-ansi-term.scm <espectalll[m]>how is it possible that I just talked about it yet still forgot <OrangeShark>gnu packages is just how guix organizes their own packages <espectalll[m]>this one is more of a configuration setting related to Cargo <espectalll[m]> `error: the lock file needs to to be updated but --locked was passed to prevent this` <espectalll[m]>it's about 1:30 AM here, and I've been with Guix all day already <red__>Greetings. Current NixOS user considering putting toes into the guix pool <red__>haha, any advice flr someone familiar with one a <red__>so not starting from zeroish? <red__>what i really neex s a deep dive video where the first 40m are trying to convince me that deterministic and immutable is good <rekado_>ha, that was simple: I just ported Yale Haskell to CLISP. <rekado_>porting it to Guile turned out to be a lot more difficult <rekado_>red__: aren’t you already convinced of this coming from NixOS? <red__>i'm actually deleriously happy with NixOS with one fundamental exception. <red__>i need to escape systemd to a more sane init. <red__>and i've been looking for a good excuse to learn a lisp <red__>so a look at guix seemed more than appropriate <rekado_>red__: can’t say if shepherd is “sane”. It certainly does much less than systemd, for better or worse. <red__>I'm less concerned by how processes and daemons start and more concerned about the insane attack surface that's in the one process that can't die. <red__>I wish I understood this obsession to make init more than 20 lines of code :-/ <red__>given that sheperd comes from dmd which comes from hurd... does that mean that there's a potential for a guix/hurd? <rekado_>what makes you say that dmd comes from hurd? <red__>"Its development was then closely related to the GNU Hurd, although it has always supported GNU/Linux as well" <rekado_>aside from that: yes, Guix already runs on the Hurd and can build native Hurd applications, but we don’t have a prebuilt GuixSD image for the Hurd. <red__>" It is intended for use on GNU/Hurd, but it is supposed to work on every POSIX-like system where Guile is available" <rekado_>red__: I’m not sure if dmd was ever used on the Hurd, to be honest. <red__>I'm a huge fan of microkernels... an opportunity to leverage hurd is a huge plus in my bpok <red__>may even put some dev cycles into that <albertoefg>sneek: later tell lfam that i wish him happy holidays <red__>Well, here goes my first guix system init, wish me luck!~ <red__>although it's just hanging... <red__>I'll let it run overnight I guess (it's 02:51 here) <red__>ah, thar she goes... mirror.hydra.gnu.org! <nand1>red__: I was getting that too on a recent install, but will eventually count up in percentage instead of just displaying 100% <red__>Thanks, I'll let it run then. Later! ***orly_owl_ is now known as orly_owl
<ng0>Hi. There hasn't been any major breakthrough for cupsd with printers requiring the HP printer driver/modules like (most of) the DeskJet series does? <ng0>I mean, printing without requiring packaging/using the HP modules is not possible.. right <ng0>But can we not just package hplip? The license on the surface is GPL2 <ng0>I don't know about blobs etc <rekado_>for some HP printers you’ll need hplip <ng0>I understood hplip as controversal, but maybe my memory is wrong about this <ng0>I think the question is, could I package hplip and would it be accepted, or would it be against our guidelines? <ng0>but we already have hplip.. my bad, I did not search <ng0>If I understand our cups-service documentation right, I need to add hplip to: cups-configuration parameter: package-list extensions .. or maybe it'll just work, I'll try in a few days <ng0>we use "lpadmin" for cups admins, not "lp", correct? <ng0>erronous parameter.. hm, I don't need to print right now but getting hplip in there shouldn't be too hard <ng0>what would be the absolute path to point hp-setup to for the ppd files? are they in /run/current-system/ or do I rather use one of the user profile .guix-profile paths? <ng0>dring hp-setup -i for the .ppd.gz files in hplip I get: TypeError: cannot use a string pattern on a bytes-like object <adfeno>Was this error raised by hp-setup or by Guile/Guix? <ng0>I get to the point where I can specify the ppd file, and when I enter the path to the file in /home/ng0/.guix-profile/share/ppd/HP/model-i-use.ppd.gz <adfeno>Although I'm not an expert tech person, I'll try helping you out.... I just have to see what hp-setup expects to receive as an argument for -i. <ng0>well i use -i as it is interactive setup <ng0>I'm used to having the qt setup, but for whatever reason we do not build thatr <adfeno>Do you by chance specify the path tothe ppd.gz file directly followed by the -i option? <ng0>I can paste the full error <ng0>-i is dialogue based <adfeno>Hm... And are you planning to automate the hp-setup -i usage somehow? <adfeno>(I.e.: Create a Guix recipe that uses `hp-setup -i`) <ng0>I rarely print, and I'm okay with just using the setup <adfeno>Hm... This is mostly interesting, so it really seems to be an hp-setup specific problem then... Well... I'll try to dive into it to see what I can find out. <ng0>I know the printer works because it worked on Gentoo this way <ng0>what I don't remember is wether the files on gentoo where .gz aswell <ng0>I'll try without -i now <ng0>was there a reason why Qt5 support wasn't added to hplip? <adfeno>Hm... a bug in hplip's setup.py... Good thing the backtrace isn't that long (I easily get lost when following backtraces, specially if the codes don't have comments explaining what to expect for). <adfeno>Is the `hp-setup` provided by the hplip package? <adfeno>(I don't remember, this is why I ask) <adfeno>OK... I'm getting the sources now. <ng0>I think I have the time to add pyqt5 support in two days <ng0>do you understand what the nickname problem is about? nickname_pat is mentioned in line 72 <adfeno>ng0: Still downloading sources... :) <adfeno>Now I'll read it to see if I can understand what is going on. <ng0>If I do /home/ng0/.guix-profile/share/ppd/HP/PRINTER_series.ppd or /home/ng0/.guix-profile/share/ppd/HP/PRINTER_series , the error is not found / not an ppd file, so the .gz ending is expected <ng0>we also should alter whatever hp-check uses, it checks some paths which we do not have <ng0>24 errors, 1 warning <adfeno>I wonder what does `search([Something])` and `group([Some number])` do in the Python programming language. <adfeno>These might get us the answr we need. <adfeno>Besides, I have noticed that nickname_pat seems to be a regular expression of some sort, it seems to expect "NickName:" in the begining of a string. <ng0>the printer "nickname" is asked for AFTER pointing to the ppd file if I remember it correctly <ng0>if it greps for the printer name based on the queue name and explicitly tries not all small letters (queue name is misc cases), it will fail <ng0>I've got some debug output.. but I need to understand it in relation to my printer name <ng0>maybe it doesn#t understand the ending _series <adfeno>If I got line 560 right: it might do something like this: take the regular expression defined in nickname_pat... <adfeno>... , use it to search for a match inside "nickname" variable (and return only the matching part), and use this result to return only the last match that corresponds to the first regexp group defined (hence `group(1)` which always prints only the last match of group 1). <adfeno>Now, it's only a matter of understanding what are athe contents of the "nickname" variable. <ng0>we are not flexible in using either old or new algorithm in the build or both at the same time? <adfeno>ng0: Sorry, but I'm afraid my limited knowledge can't answer the last question. <ng0>I also read complains about missing various python libs, so I'm not sure wether those need to be propagated and hplip just builds currently but doesn't really work <ng0>our printer has no access to the network in any way, so I guess I could also paste the whole verbose outputs <adfeno>Ok... so `nickname = gzip.GzipFile(file_path, 'r').read(4096)` tries to extract the gzip file and read the first 4096 bytes to be put inside the "nickname" variable. <ng0>extract.. in the store? <adfeno>ACTION wonders what could these 4096 bytes hold. <ng0>would the output of hp-setup -i -a -g help? that's --automic --debug --interactive <ng0>the way I read it, for my model no matching ppd file is found in the .dat file so it falls back to old algorithm <ng0>but the section of the printer is found <ng0>when it comes to the printing queue setup, the ending "_series" part is dropped, if the .ppd.gz is search for without the _series, it could fail <adfeno>Just one question: have you got past the error you informed me earlier (that is: TypeError: cannot use a string pattern on a bytes-like object)? <adfeno>Oh... OK then, so we are indeed working at the stage-or-problem. <ng0>detection succeeds, but as soon as the ppd file needs to be located and then manually specified, it fails <ng0>*printer detection that is <adfeno>ng0: I guess we must try what you suggested: hp-setup -i -a -g <ng0>another thing.. I just tried to add it simply in the cups webinterface, with the ppd defined, and I get a complain that hpcups is not available <ng0>Idle - "File "/gnu/store/pd200v2q8vdxy6ycsxjsskxavc5q2jvk-cups-server-bin/lib/cups/filter/hpcups" not available: No such file or directory" <ng0>As this never connected to the internet or network printer is pretty save, is an email to guix-devel@ as a paste okay for you? <adfeno>Well... It's better to email it to guix-devel since I don't know if I'll be able to solve it. <adfeno>And also, this is strange.... the recipe for cups currently enables hpcups <adfeno>ACtually, the recipe for hplip enables it. <ng0>oh, I had to chnage a bit, hpcups is recognized <adfeno>I just wonder if hpcups is really provided by some package. I mean, the recipe for hplip seems to enable it, but I at least am not sure if hplip provides it. <ng0>Sat 24 Dec 2016 01:59:10 PM UTC <ng0>"Color Manager: no profiles specified in PPD" <ng0>do I need cups in global packages available in addition to the service? I thought just having the service is enough <ng0>I need to go now.. thanks for your help <jmd>Are we building staging or what? <taylan>ACTION wonders who's in charge of the website <lfam>I just joined; which website? <sneek>lfam, albertoefg says: that i wish him happy holidays <taylan>lfam: I mean gnu.org/s/guix. a small text change to the About page should be trivial to do I think so I wanted to ask them if they've seen the related bug report. (I'm now wondering if there was a reason, like FSF requirements, to list GuixSD as a "GNU/Linux distribution" on that page though...) <lfam>I don't know if there's a particular we reason we say GNU/Linux instead of GNU. <lfam>It's funny how wikipedia turned out. It's not that different from the old paper encyclopedia model now ;) <taylan>lfam: what's the "old paper encyclopedia model"? :) <lfam>Petulant editors guarding their little kingdoms ;) <lfam>It's an uncharitable thing to say, but there's some human truth in it, I think <lfam>I remember when a person could actually do "drive-by" edits of wikipedia <taylan>yeah Wikipedia is just turf wars when it comes to somewhat subjective/opinionated topics... <taylan>lfam: thanks for the link to the artwork repo. I sent a patch to my bug report now :P <taylan>'git blame' didn't indicate anything like a switch from "GNU distribution" to "GNU/Linux distribution" on that page; it said the latter ever since the whole paragraph was added. besides if there were a policy for it, I'm pretty sure it would apply to the home page as well... <taylan>apparently it was Ludo who added the paragraph so I guess I can ask him when he's around <lfam>Maybe we should keep the word "Linux" somewhere or people might think that Guix only works on Hurd. I've had to correct that misconception twice! <lfam>And many other misconceptions... it's a bit annoying to explain yet again that Guix is not a "Scheme wrapper of Nix" <lfam>"The amount of energy necessary to refute bullshit is an order of magnitude bigger than to produce it." <lfam>Now I'm going off-topic ;) <kqb>Hi, I'm trying to install guix in a QubesOS HVM. <kqb> (1) There is a problem with the network <kqb>(2) a nix post said, it might be useful to disable ip6 <kqb>how do I go about solving (1) maybe with the help of (2)? <kqb>(# dmesg) does not yield anything that indicates a problem with the network interface. <kqb> I looked for "net", "IP", "link". <taylan>guix master branch failing to build with guile 2.2, saying module (json) not found. bummer. wonder if I did something wrong.