<civodul>maybe we could still get rustc-bootstrap at least
<civodul>i suppose this one isn't going to change significantly?
<avoine>_myglc2: that would be my list : python-flake8 python-virtualenv python-tox python-nose2 python2-jedi python-jsonrpclib
<avoine>_myglc2: are you doing web with django or just python?
<dvc>the version might - currently it's using beta, it should use the stable release. In my version I'm using nightly. It depends on which version of rustc makes it into master, I haven't worked on that yet.
<avoine>also you need service_factory from pypi do get the anaconda-mode to work
<htgoebel>_myglc2: Python on GuixSD is not different then on any other Linux distribution.
***[0xAA] is now known as Agent170
***[0xAA] is now known as Agent170
<_myglc2>htgoebel: Thanks. "Python on GuixSD is not different..." is conceptually true. But given that GuixSD package "coverage" is less I want the most well-worn path for my emacs python envionment ;-)
<_myglc2>amz3: you said "... and install the associated pip". Don't understand what you mean. python.scm only has one python-pip doesn't it?
<amz3>_myglc2: it's python-pip then, in debian there pip2 and pip3...
<_myglc2>rekado: You said "I'd like to suggest to only install packages via Guix". Believe me I prefer this. My experience w/ Guix packages is excellent. But in this case I just want to smoke-test scrapy. I hit a problem getting it installed on Guix so I switched to a Debian server & did 'apt-get install python-scrapy' ... doesn't work there either. Arg!
<_myglc2>htgoebel: what do you mean "Guile suffers "batteries included"."?
<ng0>as long as I'm not sure i don't want to attract any attention to it, but it would not be hard to find my bugreports.
<ng0>so it's arm, and what else? just for building there should be no difference between asus c201 or what it was and novena, right? or is it a specific version/subset of arm?
<ng0>I know most of the story around novena, but what reason for someone just building software is there compared to other arms? do they construct something differently?
<ZombieChicken>I just posted a link to the article pointing out Intel's ME system and Novenu as an alternative and hopefully sane option
<ng0>I'm affraid it's not just post 2009.. it's at least post 2001 or somewhere waround that time. I had a discussion about this earlier this year.
<ZombieChicken>Hmm. Apparently my desktop isn't affected by that little security nightmare. My old AMD system is just too old
<ZombieChicken>ng0: According to a discussion I had with someone in another chat, it varies between chipsets. Post-'09 seems like the point where it was standard. Prior to that you could get a system without ME on it
<ZombieChicken>From what I've seen, his reponse is fine, although he isn't being helpful in the least
<ng0>yes.. but i can't create the patch, that language is not my field of expertise
<ZombieChicken>ng0: Then drop the package, close the related a WONTFIX and move on
<ZombieChicken>after saying you can't patch it yourself, and upstream doesn't care
<mechanical>I'm presumably finished with writing a package definition, but I'm unable to figure out how to place it in the proper location for guix build to use. I would appreciate some guidance with this.
<ng0>that's my last attempt before I do so.. in 7 months no one came forward.. but, but we have much older bugs.
<ng0>look at the price of neo900.. and they just add to old pieces
<mechanical>So, not trying to be a bother, but I was unable to find the solution to my problem in the documentation. I've what I believe will be a working package definition, but I'm unable to attempt to build it. I'm rather stuck.
<rekado>my x200s comes with a GPRS modem card and since I never use my phone anyway I put my SIM card into the modem.
<rekado>yes, what ng0 says is important. A Guile module’s name is directly mapped to its path from a given root directory.
<mechanical>It's my understanding that I should be able to contribute packages without needing the entire git repository. I should be able to create diffs of the relevant files and send those manually, or is this considered to be in poor form?
<rekado>mechanical: that’s not so good for at least two reasons.
<rekado>the first is that new modules also need to be registered in gnu/local.mk
<rekado>your manual diffs wouldn’t include those changes.
<rekado>secondly, with patches formatted via “git format-patch” we also get a little extra info like the committer name and the time of the change. It’s very convenient for us to apply patches like that.
<mechanical>I'll keep all of this in mind when I contribute a package. Thanks again. Goodbye for now.