Playing with this now myself. Is there a not stupid way to create & install an actual binary, instead of using npm start to kick it off? So far the only thing I've found is to just extract the .deb file (either direct from GitHub or make it myself) and copy the executable over to /usr/local/bin, but ...

Huh...I thought the whole thing freezing up was a hardware issue on my end. Exact same symptom, everything stopped except for the mouse. I opened up my computer and found several dust bunnies had colonized it, since evicting them things seem to be better, but it's only been a day or two.

I set up an overlay today that might work for you as well:

https://github.com/iwoloschin/overlay

It's a work in progress, and it's only tested on my Funtoo box (which is why wxPython is included), but it compiles and it seems to work. This is for the brand new, just release 4.0 Stable RC. It ...

Tried that and it didn't seem to work.

Is it possible to just remove the older ebuild from the tree? Or would users (or developers?) still need to hard mask the older package to remove it, and install a new one?

Well, masking the older package seems to work, but isn't ideal. Is there any way to automatically include such a mask in an overlay?

I'm trying to write a new ebuild to support an upcoming stable RC for the KiCad project. Unfortunately, the latest ebuild looks like this:

sci-electronics/kicad-20130518.ebuild

The KiCad developers have decided that the new stable release, the first in several years, will be called 4.0, resulting ...

Well talk about obscure and confusing issues. Turns out the version of SDDM shipping with Gentoo does not like ZSH, and possibly more specifically, Prezto.

https://github.com/sddm/sddm/issues/352

Everything seems to be working now.

I can't help with lightDM as I have zero experience with it but I will mention that you can in fact use sddm for the display manager with OpenRC and Plasma 5. It mostly works fine and I've been using it for months. However that could change and there are technical reasons to switch. I believe it is ...

I just noticed this too. Probably a bug?

I was going to go to sleep early tonight...

You can try this overlay:

https://github.com/aegypius/overlay

Unfortunately, I've got trouble with getting atom-shell (now electron) built, seems that npm hates sudo or something? It's unclear to me, and I've never really used it before.

Will kde-apps-15.04 get fancy pre-made package.* files in the overlay? It looks like Yamakuzure is just making his own package.* files, correct?

that might be a good question for the guys at crosstool-ng, the guy which was in charge of adding it to crosstool-ng was using arm in the first place I think.

I might look into this more. Turns out I'm going to be working all weekend, so this might turn into a longer term project then I was ...

Curious if anyone has thoughts on using MUSL for ARM, specifically a BeagleBone Black? I might try it just because, though I'm not sure if it's actually worthwhile or not.

For what it's worth, I used a Beaglebone Black last winter to detect our cellphones on the home network, and use that to control my Nest thermostat (if we're home, turn on the heat, if we're not, turn it off). It was running Debian, but I'm trying to put Gentoo on it now (haven't had time). It's ...

I just ran into this same problem...any definite solutions?

I'm trying to setup a fresh install w/ ati-drivers. I'm using gentoo-sources-2.6.28-r1, ati-drivers-8.561, and xorg-server-1.5.3-r1. My main problem is xorgcfg and X -configure both throw errors:


~ # xorgcfg

X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0 ...

I've got a brand new install (amd64) using baselayout-2/openrc, trying to install ati-drivers, which required upgrading to some testing branch (~amd64) packages.

I have udev-135-r2, and hal says the following:

[blocks B ] >=sys-fs/udev-125 (">=sys-fs/udev-125" is blocking sys-apps/hal-0.5.11-r1 ...

d2_racing:

I'll give it a shot tomorrow, but I was getting some funky USB error messages (on boot) that make me think either that the USB wireless adapter, or worse, the USB controller, just died...which would kind of explain the nonsensical lack of errors I've been getting. I've about had it with ...

Hmm...now it appears that the network won't start up at all. I turned off the machine last night, and it's telling me that scanning is not supported by the device when trying to start the network.

Just to walk through the process manually I tried to rmmod the module (zd1211rw) and it hung the ...

I apologize upfront for the lack of details, but I'm not quite sure what to make of this problem.

I have an amd64 machine, with a Belkin USB wireless adapter, using the zd1211rw driver. I use Synergy between the Gentoo computer and a Vista laptop, and the first problem I noticed was Synergy kept ...

So I took a look at /var/log/messages and it's telling me that the authentication to the AP is timing out. From that, obviously it's not going to get an IP. I apologize for no straight logs, but as I have no internet on the computer in question...hard to get logs off of it beyond sneakernet...which ...

Updated kernel to use b43legacy, haven't touched the kernel since though (and it was working). Using wireless-tools as my roommate's router is "only" using WEP, but we're not too afraid of wardrivers. Didn't notice anything in /var/log/messages, but I can look again tonight. The problem I'm having ...

I have a BCM4306 Rev 02 card, using b43legacy as a driver. I had everything working great, until one night last week everything just stopped working. Right now when I try to initialize the wireless network I get this.


root# /etc/init.d/net.wlan0 start
* Starting wlan0
* Configuring Wireless ...

As the subject says, this is a pretty straightforward problem.

I have amd64, gentoo-sources-2.6.25-r7, with a Broadcom 4306 (rev 2) using the b43legacy driver. Internet works great! However, I just noticed, while upgrading some packages, portage was constantly getting stuck and not prefetching ...

follow the directions, but if you need to download a package, grab the files ( can be seen by running the emerge, seeing the failures, or by looking at the ebuild), and put them into /usr/portage/distfiles.

hih.

Heh, I didn't think of doing that. However, the one problem I'm concerned about ...