Hi,
I am looking for some help with my PR which updates libuv to the most recent
version:
https://github.com/NixOS/nixpkgs/pull/14973
I want to introduce nodejs 6.0.0 which needs libuv 1.9.0 and I am blocked by
this. The PR will always fail with travis because nox-review needs too long. I
Domen Kožar writes:
> It doesn't build PRs, just updates the status.
>
Does this mean it can build specific branches (master, release-16.04..)
and set the commit status on those commits? ie: doesn't have anything to
do with pull request statuses?
Best,
Graham
It doesn't build PRs, just updates the status.
On Wed, Apr 27, 2016 at 9:44 PM, Ericson, John
wrote:
> Support for hydra to build github PR has been added for a few weeks now in
> https://github.com/NixOS/hydra/pull/280 . What's the next step for
> actually using this
Support for hydra to build github PR has been added for a few weeks now in
https://github.com/NixOS/hydra/pull/280 . What's the next step for actually
using this with nixpkgs and hydra.nixos.org?
On Tue, Feb 23, 2016 at 4:46 PM, Ericson, John
wrote:
> > S3 and Hydra PR
Hi,
did you try asking the systemd people directly ? I think they will best
know as it's really a functionality of their sub-system.
Best,
z
On Tue, 26 Apr 2016 at 12:55 4levels <4lev...@gmail.com> wrote:
> Hi Nix-devs,
>
> is it possible to have the startAt attribute take a given timezone in
> You are right, the „multiple releases“ approach clogs the repository. In
general it would be a lot more favourable if we didn’t have to check in
these thousands of package descriptions but could generate them from hackage
IMO an advantage of checking package metadata into git is that we notice
On 16-04-25 03:15pm, Eric Merritt wrote:
> I think these strongly win out, at at least for the Erlang/Beam world. The
> downside is that grepping the
> nixpkgs repository (my default way to search for a package) doesn't work
> nearly as well.
You are right, the „multiple releases“ approach