<ng0>rekado: thanks for the axoloti links and work on it. I've been talking with tg about music yesterday.. reflected a bit and decided I need to pick up my dormant music project again and start now elsewhere, explore electronics and generated/coded music etc..
<ng0>I'll package some of the applications (like supercollider) in the next time for myself.. will throw them to the list
<jmd>Dawgmatix: Do you have a dhcp server on that network?
<ng0>I'm also sorry in advance for this, I'll have to more or less revert the mailmap patch.. did some calculations and reasoning (about domain/hosting related stuff) with myself and in the longrun I'll be more flexible when I keep the n0.is domain .. so I'll send a patch today for this
<ng0>and before I start.. no one happens to be working on supercollider package currently?
<ng0>so I some some experiments... and I think our primary web browsers (epiphany, icecat) lack whatever is needed to log into gnusocial. So far I could only log in using reset password links.
<ng0>the other theory is that gnusocial has problems in the login form. so far it's just me, so i don't know if this is just introduced by mistakes I do. this is without librejs (deactived)
<rekado>civodul: I pushed a patch to core-updates to fix the build of tcsh, whose failure is responsible for many of the failures on core-updates. Should we start a new evaluation? (Or will this be picked up automatically?)
<civodul>rekado: yes, you can go ahead and start a new evaulation
<civodul>there's no periodic evaluation of that branch
<wingo>i was patching configure.ac when i needed to patch configure; with that, test pages should work. anyway. as long as we are rebuilding the world we should push the newest version of that first patch too :)
<ng0>uhmm... I think when I tried to move my sdf.org account and after 3 weeks when nothing happened and previous communication failed and I opened a complaint at paypal, I think sdf.org might've just dropped my account.. or it's just the server right now. but the one font we hosted there, you might want to check up on that
<ng0>what the...? is this a mature way.. or any way to solve a question of payment? wow
<ng0>so.. font-un is now broken and I will certainly not use sdf.org anymore until paypal reverts the payment. or anymore afterwards. so much for "lifelong" membership... does someone have a server to host this font at? upstream is still broken, and I won't have a server for some months
<ng0>just logged in, yup the canceled this lifelong account. haha...
<ng0>it's not just deactived, they just erased it. so if I would have had any personal data on there the raging admin would've just destroyed it.
<Dawgmatix>Figured the dhcp issue out, on an ubuntu system it appears that you are better off not specifying -net directives to qemu
<Dawgmatix>If I drop the -net directives, the ethernet interface changes from eth0 to ens3 and can indeed get an ip address
<Dawgmatix>Any pointers on best way to achieve the following -> i would like to build a custom kernel, and i would like to build gcc from trunk
<rekado>Dawgmatix: to build GCC with different sources it's easiest to inherit from the existing "gcc" package using (inherit gcc)
<rekado>Dawgmatix: then override the source field and add native inputs to generate the configure script.
<jmd>Why is it called /gnu/store and not /gnu-store ?
<civodul>wingo: oooh, sorry for overlooking that, i'll apply the new patch then
<ng0>their way of moving accounts is unlike what they document in public. also, font-un got an update, maybe the mirror can be dropped.. I'll see it with the update
<lfam>My understanding of the analysis given by upstream is the impact of this bug is mostly mitigated in the version of dbus we package, but I'd appreciate it if someone else would read that message and the linked bug report
<rekado>lfam: I read the message and understood that our version is not affected.
<lfam>I'll send an update patch for core-updates. We can take it or leave it but at least the patch will be available
<efraim>i have perl-module-build on core-updates building successfully atm
<lfam>rekado: To clarify, I think our version does have the format string problem, but only the owner of the bus can pass formatted strings to the vulnerable code. So only root can trigger the bug in our version, which is undesirable but not really a big issue. That assumes that upstream's analysis is correct and that only the bus owner can pass formatted strings to the broken code
<lfam>Hm, turns out we weren't running the Borg test suite. Older python versions did not report an error if `python setup.py test` did not find a test suite, but email@example.com does. So we see the problem now on core-updates.
<lfam>nckx: On core-updates, with firstname.lastname@example.org, we realized that we weren't actually running the borg test suite. Master's email@example.com doesn't return an error if `python setup.py test` finds no tests, but firstname.lastname@example.org does.
<lfam>So now I am working on making those tests run and pass
<lfam>I'm not stuck yet, but I will try picking your brain if I do get stuck
<lfam>Looks like we need to invoke the tests with `tox` and add some dependencies