ekleog changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html https://r13y.com | 18.09 release managers: vcunat and samueldr | https://logs.nix.samueldr.com/nixos-dev
orivej has quit [Ping timeout: 246 seconds]
<dtz> anyone have thoughts re:https://github.com/NixOS/nixpkgs/pull/57778 ?
<{^_^}> #57778 (by dtzWill, 21 hours ago, open): xorg: batch of updates, bump luit
drakonis_ has joined #nixos-dev
ajs124 has left #nixos-dev [#nixos-dev]
drakonis has quit [Quit: WeeChat 2.3]
jtojnar has joined #nixos-dev
jtojnar has quit [Client Quit]
orivej has joined #nixos-dev
johanot has joined #nixos-dev
cransom has quit [Ping timeout: 258 seconds]
init_6 has joined #nixos-dev
drakonis has joined #nixos-dev
init_6 has quit [Ping timeout: 250 seconds]
<roberth> suppose I backport to 19.03 two tiny package additions that aren't even built by hydra, is that reasonable or bad?
jtojnar has joined #nixos-dev
<aszlig> samueldr: Going to merge #57641 in the evening today, unless there is heavy opposition.
<{^_^}> https://github.com/NixOS/nixpkgs/pull/57641 (by aszlig, 3 days ago, open): linuxPackages: 4.14 -> 4.19
johanot has quit [Quit: WeeChat 2.4]
<aszlig> samueldr: as mentioned in the last comment, i opted for a qemu patch instead, unless this is fully resolved upstream
<aszlig> s/unless/until/
<aszlig> and i highly doubt that anyone would complain like: "hey, since linux 4.19 overlayfs passes O_NOATIME to lowerdir and i want to have that on my 9p filesystem that's _not_ mounted with noatime"
<aszlig> it's even weird that 9p even handles that flag and doesn't ignore it like all the other networking file systems in linux
<samueldr> qemu patch sounds good
<samueldr> wasn't fond of the kernel patch (until it went through upstream), but I think patching qemu should be fine instead
<aszlig> samueldr: yep, especially because the patch is very low-impact and only removes one line
ajs124 has joined #nixos-dev
<lewo> Hi. It would be nice to publish an Openstack imge on the NixOS homepage. I'm wondering how it could be uploaded. It is already done for a virtualbox image i guess. Someone could help me on that?
<{^_^}> nixos-homepage#266 (by nlewo, 4 weeks ago, open): Publish Openstack image
<simpson> lewo: https://github.com/NixOS/nixos-homepage/blob/master/nixos/download.tt looks like the page to change. IIUC all of those images are Hydra-built, so we'd probably want to take that route for your image too.
<lewo> simpson: thx, my issue is more on the second part: how the image is published! Do you know which Hydra job publish the virtualbox image for instance?
<simpson> lewo: I think that https://github.com/NixOS/nixpkgs/blob/master/nixos/release.nix is the right place to look.
<lewo> simpson: The ova link is https://releases.nixos.org/nixos/18.09/nixos-18.09.2337.5d972dd2c94/nixos-18.09.2337.5d972dd2c94-x86_64-linux.ova which doesn't seem to be an hydra build product download link.
<simpson> lewo: Sure, but that link seems to have started out in download.tt as "[%prefix%]/nixos-[%latestNixOSRelease%]-x86_64-linux.ova" which seems like it was built as part of a release.
<lewo> ok, thx. I will submit a PR to add an openstack image in release.nix.
<lewo> simpson: but how a release is created?
<lewo> Because only some specific evaluations can be downloaded from release.nixos.org
<simpson> lewo: Dunno. Haven't really paid attention to that part of things. Are you wondering how long it might take for your image to show up? What's your larger plan and timetable?
<lewo> simpson: yes, exactly. Actually, I have time. But I would like to know when it will be available from release.nixos.org in order to test it and create a PR in the nixos homepage repository.
<simpson> lewo: I think that you'd test the image using your local nixpkgs, but I don't know much about OpenStack.
<lewo> This is already done.
<srhb> After that, it'll update on each succesful run of a nixos test set.
<lewo> By "test", I meant "test the download link"
<srhb> But someone else can probably answer this with more certainty (eg. the committers relevant to those lines)
<lewo> Ok. I'll submit PRs and ping them if needed. Thx!
yl has joined #nixos-dev
drakonis has quit [Quit: WeeChat 2.3]
ajs124 has left #nixos-dev [#nixos-dev]
cransom has joined #nixos-dev
ajs124 has joined #nixos-dev
drakonis has joined #nixos-dev
drakonis_ has quit [Ping timeout: 246 seconds]
drakonis_ has joined #nixos-dev
drakonis has quit [Read error: Connection reset by peer]
chaker has quit [Ping timeout: 252 seconds]
drakonis has joined #nixos-dev
drakonis_ has quit [Read error: Connection reset by peer]
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 258 seconds]
drakonis has joined #nixos-dev
drakonis_ has quit [Ping timeout: 245 seconds]
drakonis has quit [Read error: Connection reset by peer]
drakonis has joined #nixos-dev
<gchristensen> a nixops "upload to cache, then deploy" option would be cool
drakonis has quit [Ping timeout: 264 seconds]
<clever> gchristensen: of note, nixops dump-nix-paths, will give the top-level storepath, that depends on every machine
<clever> you can then use nix copy s3://, to upload it
<gchristensen> nice
yl has quit [Ping timeout: 244 seconds]
drakonis has joined #nixos-dev