Hi all,
Builds are failing on hydra and the logs show issues with disk space.
Also, a lot of sqlite db busy warnings pop up, but I was told these
are harmless.
http://hydra.nixos.org/build/3336787
Can anyone free up some space / garbage collect the build farm?
Or will this be run as a cronjob
Hi Mathijs,
Is anyone still using linux 2.6.15 or 2.6.35 or 3.1 or 3.3 or 3.5 ?
I'm still using 3.5. I cannot upgrade to 3.6 yet, because my wireless
interface (iwlwifi: Intel Centrino Advanced-N 6205 AGN) won't work with
the new kernel for some reason.
Take care,
Peter
All hydra build machines have nightly garbage collects, I think of about
100-200G. Perhaps it was a busy day and filled disk up. Currently the
machine looks fine. Thanks for the report.
Cheers,
Rob
On Sun, Nov 18, 2012 at 2:01 PM, Mathijs Kwik math...@bluescreen303.nlwrote:
Hi all,
Builds
Quoting Peter Simons (2012-11-18 14:30:18)
Hi Mathijs,
Is anyone still using linux 2.6.15 or 2.6.35 or 3.1 or 3.3 or 3.5 ?
I'm still using 3.5. I cannot upgrade to 3.6 yet, because my wireless
interface (iwlwifi: Intel Centrino Advanced-N 6205 AGN) won't work with
the new kernel for
Hi all,
I broke the build again :D
I traced it down to a place in my expression [1] line 16.
A simple fix seems to be to assert that licenseAccepted is true as a
first line in the function.
However, this has the effect of hiding the entire package, instead of
showing the helpful message I want to
The only way to make this work is make hydra accept the license - which
would be bad - cause you could install the package by one click
install without setting the option.
For this reason I'd suggest manually building it only.
Thinking about it again - this is not even enough. If you have two
On Sun, Nov 18, 2012 at 5:49 PM, Marc Weber marco-owe...@gmx.de wrote:
The only way to make this work is make hydra accept the license - which
would be bad - cause you could install the package by one click
install without setting the option.
For this reason I'd suggest manually building it
Hi Mathijs,
Is anyone still using linux 2.6.15 or 2.6.35 or 3.1 or 3.3 or 3.5 ?
I'm still using 3.5. I cannot upgrade to 3.6 yet, because my wireless
interface (iwlwifi: Intel Centrino Advanced-N 6205 AGN) won't work with
the new kernel for some reason.
iwconfig stopped working as Wireless
You can builtins.trace a message, then cause failing assertion.
AFAIK assertios show file, line. Thus its easy to lookup.
Maybe it would be a use case for a soft throw behaving like a failed
assertion - thus I'd not worry too much.
Marc Weber
___
On Sun, Nov 18, 2012 at 6:26 PM, Marc Weber marco-owe...@gmx.de wrote:
You can builtins.trace a message, then cause failing assertion.
AFAIK assertios show file, line. Thus its easy to lookup.
Maybe it would be a use case for a soft throw behaving like a failed
assertion - thus I'd not worry
On Sun, Nov 18, 2012 at 6:17 PM, Michael Raskin 7c6f4...@mail.ru wrote:
Hi Mathijs,
Is anyone still using linux 2.6.15 or 2.6.35 or 3.1 or 3.3 or 3.5 ?
I'm still using 3.5. I cannot upgrade to 3.6 yet, because my wireless
interface (iwlwifi: Intel Centrino Advanced-N 6205 AGN) won't work with
On Sun, Nov 18, 2012 at 11:17:57AM +0100, Mathijs Kwik wrote:
Is anyone still using linux 2.6.15 or 2.6.35 or 3.1 or 3.3 or 3.5 ?
If not, we should probably take them out, as they won't be receiving
updates any more.
We still use the kernel headers from 2.6.35. As for 2.6.15 or anything .35
On Sun, Nov 18, 2012 at 8:14 PM, Lluís Batlle i Rossell
vi...@viric.name wrote:
On Sun, Nov 18, 2012 at 11:17:57AM +0100, Mathijs Kwik wrote:
Is anyone still using linux 2.6.15 or 2.6.35 or 3.1 or 3.3 or 3.5 ?
If not, we should probably take them out, as they won't be receiving
updates any
some news about this issue:
as described in [1]
grep -i notif .xsession-errors
plasma-desktop(3192)/plasma StatusNotifierItemSource::refreshCallback:
DBusMenu disabled for this application
plasma-desktop(3192)/plasma StatusNotifierItemSource::refreshCallback:
DBusMenu disabled for this
Quoting Mathijs Kwik (2012-11-18 18:39:59)
On Sun, Nov 18, 2012 at 6:17 PM, Michael Raskin 7c6f4...@mail.ru wrote:
Hi Mathijs,
Is anyone still using linux 2.6.15 or 2.6.35 or 3.1 or 3.3 or 3.5 ?
I'm still using 3.5. I cannot upgrade to 3.6 yet, because my wireless
interface (iwlwifi:
Mathijs Kwik writes:
Ok, so this means that setting networking.wireless.driver to
nl80211 would do the trick.
Indeed, that solved the issue for me. Thanks for your help, guys!
As far as I am concerned, I'm fine with 3.5.x being removed.
Take care,
Peter
On Sun, Nov 18, 2012 at 11:39:55PM +0100, Peter Simons wrote:
Mathijs Kwik writes:
Ok, so this means that setting networking.wireless.driver to
nl80211 would do the trick.
Indeed, that solved the issue for me. Thanks for your help, guys!
As far as I am concerned, I'm fine with 3.5.x
Hi,
I think initially some of the old kernels were re-added by a colleague
of mine to allow continuous integration testing of a kernel module
against a variety of Linux versions.
It’s no longer used, but that kind of use may still make sense.
Thanks,
Ludo’.
Hi,
On Sat, Nov 17, 2012 at 4:59 PM, Marc Weber marco-owe...@gmx.de wrote:
I'd force the user to set a config option like this:
~/.nixpkgs/config.nix:
{
proprietary-licenses-accept.your-package = true;
}
and only allow installing the software if this is enabled.
At least this requires
On 11/18/2012 08:00 PM, Nicolas Pierron wrote:
Hi,
On Sat, Nov 17, 2012 at 4:59 PM, Marc Weber marco-owe...@gmx.de wrote:
I'd force the user to set a config option like this:
~/.nixpkgs/config.nix:
{
proprietary-licenses-accept.your-package = true;
}
and only allow installing the
Isn't it enough to depend on the git's hash value, eg
fetchgit { git_hash = xxx; url = yyy; }
Is compromising a git repository (even using shallow clones) that much
easier than compromising a .tar.* file protected by sha256?
In anyway you have to find a hash collision.
A lot of foreign tools
On Sun, Nov 18, 2012 at 10:11 PM, Marc Weber marco-owe...@gmx.de wrote:
Isn't it enough to depend on the git's hash value, eg
fetchgit { git_hash = xxx; url = yyy; }
Is compromising a git repository (even using shallow clones) that much
easier than compromising a .tar.* file protected by
On Sun, Nov 18, 2012 at 10:24 PM, Nicolas Pierron
nicolas.b.pier...@gmail.com wrote:
On Sun, Nov 18, 2012 at 10:11 PM, Marc Weber marco-owe...@gmx.de wrote:
Isn't it enough to depend on the git's hash value, eg
fetchgit { git_hash = xxx; url = yyy; }
Is compromising a git repository (even
On Mon, Nov 19, 2012 at 1:01 AM, Ludovic Courtès l...@gnu.org wrote:
Hi,
I think initially some of the old kernels were re-added by a colleague
of mine to allow continuous integration testing of a kernel module
against a variety of Linux versions.
It’s no longer used, but that kind of use
On Sun, Nov 18, 2012 at 11:44 PM, Lluís Batlle i Rossell
vi...@viric.name wrote:
On Sun, Nov 18, 2012 at 11:39:55PM +0100, Peter Simons wrote:
Mathijs Kwik writes:
Ok, so this means that setting networking.wireless.driver to
nl80211 would do the trick.
Indeed, that solved the issue for
25 matches
Mail list logo
