<NiAsterisk>would be nice if debian jessie would get letsencrypt. says "in a few weeks" looks like I have to build it myself because I don't want to wait
<piyo>NiAsterisk: offtopic but isnt debian jessie a feature frozen distro?
<NiAsterisk>ah, yes, offtopic. sorry. I only learned about it going public now and found it in guix, but not there. yes, I have to use it because I had no choice with the current server other than debian.
<piyo>NiAsterisk: maybe you are expecting letencrypt in jessie-backports etc?
<NiAsterisk>I seem to not get notifications or playback messages here. I read the one yesterday from someone only because I read the backlog on gnunet.org, searching for something. No, I had no issues with the letsencrypt package.
<swedebugia>davexunit: ok, just a thought to continue where you left
<davexunit>swedebugia: if I find it I'll give it to you
<lfam>NiAsterisk: the sneek bot waits to give you your "saved messages" when you say something on the channel. That way, it won't give the messages to what may be an unattended IRC bouncer or something like that
<lfam>Your frustration with Debian that you mentioned earlier is one reason I like Guix so much. It's just so easy to package things for private use. And it's also easy to get those things into the GNU Guix packages as well.
<NiAsterisk>I wonder how useable guix is already on a minimal debian server image. If I don't migrate to a single dedicated server I will split what I have now into 3 individual vservers
<NiAsterisk>in-berlin (ISP) sets up some basic image with ssh access and that's it.
<rekado>I'm using GuixSD as my main system on three machines already. Very usable.
<NiAsterisk>I can't use guixsd though.. guix would work then.
<lfam>And my primary workstation (a laptop) is a Debian minimal installation with Guix
<lfam>I installed xorg from Debian because I installed the OS before I even knew of Guix but you could even install a DE from Guix on Debian.
<NiAsterisk>i use guixsd on all laptops I have, and switched from gentoo to debian on the desktop, but with servers I meant virtual servers far away (berlin) from me
<NiAsterisk>I'm not sure if I can manage to finish gnunet-gtk.. the errors I get with glade3-3.18, well I get some where searching for it on google leads me to the guix-dev list and 29 other results, that's it
<lfam>Send your current patch so we can look at it!
<NiAsterisk>something with xorg and fontpaths.. I'll do it tomorrow :) watching talks from 32c3 now
<lfam>Also, if you install do a Debian Jessie non-graphical installation, you'll probably have issues with `systemd --user`, which IMO is a killer feature of systemd. You'll have to install libpam-systemd in order to properly enable the user sessions.
<rekado>by now I'm pretty familiar with ant. What's the problem?
<lfam>Well, all the runpaths are totally wrong after the build, but I can't find an option to provide the proper paths while compiling. In nixpkgs, they use patchelf but I get the sense that we are trying to reduce use of that.
<lfam>Building now, to get a fresh log-file. The jitsi distribution tarball also has a bunch of "installation" resources but I'm not sure if they are relevant. Soon I will start asking upstream for help.
<rekado>I see that it also depends on junit for tests.
<rekado>today I finished building junit, but it's going to take me some more time before I can submit it upstream.
<lfam>I had disabled the tests for now because some of them want network access. I need to figure out how to disable those.
<rekado>Trying to find a better way to deal with Java projects using Ant.
<lfam>Yeah, I noticed you musing about an ant-build-system. Probably the right thing to do once we have a good idea about how to do it
<rekado>so, I have an updated glade package; builds fine but the tests still fail. I put this away for now.
<rekado>lfam: hardware interface for the DX7? Or software?
<rekado>I have a Wavedrum which is equally crippled by a terrible interface.
<rekado>it's fun trying to hack the firmware, though, so I'm kinda glad that it's crappy.
<lfam>rekado: Probably a hybrid. I'd have to write some hack to get the information in and out of the DX7 in "real-time" since it doesn't really have a way to do that. But it will need a physical interface of some sort. The DX7 programming interface consists of 1) a slider 2) a "+" button and a "-" button. That's it! For one of the most complicated synthesis engines ever
<lfam>I could buy a "raw" hardware interface with a lot of knobs and faders
<lfam>But create a new programming "paradigm" in the software
<lfam>To be honest, I don't know if it's really worth it. It's all digital so there's nothing special about the DX7 itself except for the 12-bit DAC, which I could just rip out and re-use and buy another of
<lfam>I might as well do it all in software. But I don't really want to build it on top of a general-purpose OS.
<lfam>And if I'm not yet skilled enough to build the interactive interface, who knows when I'll be able to learn a real-time OS or do it on a microcontroller or whatever?
<NiAsterisk>I would love an free/open hardware and software equivalent to the PODHD500 or equal gear since I stopped using rehearsal rooms (and can't play amplifiers).. that's a long dream I have. I had some sources on this.
<rekado>[offtopic] lfam: microcontrollers are very easy to learn. You could write PC software to send MIDI SysEx and have a stupid microcontroller unpack the control messages and "talk" to the DX7 by banging out some patterns.
<rekado>packaging this now. Apparently it uses Guile.
<lfam>rekado: The SysEx would probably be the easy part. The bummer is that the DX7 can't update patches in "real-time" so it's not as interactive as programming an subtractive or additive synth engine. The engine will "stop" the sound while updating the patch.
<lfam>NiAsterisk: That looks like a cool side project! I guess the interesting part would be creating the modeling engine. Then you could let people submit "patches" for different amps
<lfam>rekado: So, it's a graphical programming environment like PD but very focussed on synthesis?
<rekado>NiAsterisk: the problem with DSPs as used in digital effects is often that there is no free toolchain.
<lfam>Looks very cool. I love graphical programming for signals processing
<lfam>And most people are all too happy to "lock up" their art in proprietary systems...
<rekado>I had to write a disassembler for the SHARC ADSP in the Wavedrum to understand the code :-/ And for uploading a modified firmware I depend on the bootloader. It's impossible to get a free compiler for the DSP.
<rekado>that's why I like the Axoloti board. Free hardware design and free software. (If only it didn't depend on JavaFX...)
<NiAsterisk>(offtopic) I bought into what I have now without thinking about it back then as I used rackmounted amplifiers and other gear you can no longer sell, so software and music wasn't a thing I thought about years ago.
<lfam>How does the axoloti programming environment compare to PD?