worldofpeace changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | NixOS 20.09 Nightingale ✨ https://discourse.nixos.org/t/nixos-20-09-release/9668 | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | https://r13y.com | 20.09 RMs: worldofpeace, jonringer | https://logs.nix.samueldr.com/nixos-dev
supersandro2000 has quit [Disconnected by services]
supersandro2000 has joined #nixos-dev
jkkm has quit [Ping timeout: 244 seconds]
dmj` has quit [Ping timeout: 244 seconds]
jkkm has joined #nixos-dev
dmj` has joined #nixos-dev
rajivr has joined #nixos-dev
ris has quit [Ping timeout: 264 seconds]
orivej has quit [Ping timeout: 240 seconds]
dstzd has quit [Quit: ZNC - https://znc.in]
dstzd has joined #nixos-dev
andi- has quit [Ping timeout: 272 seconds]
mkaito has quit [Quit: WeeChat 2.9]
teto has quit [Ping timeout: 246 seconds]
<abathur> nix#4925 sounds to me like there's been a latent issue in Nix (at least 2.3.x) for a while, and that some shift (probably in nixpkgs in the past several days?) has suddenly exposed it and caused a number of people with single-user installs on Linux to present
<lukegb> Yeah, I was trying to work out if there's a particular filesystem structure or something that would cause it
<abathur> and https://github.com/NixOS/nix/issues/4295#issuecomment-738504227 feels like the first comment that has the issue drilled down far enough that someone with sufficient nix-fu may have a sense of what's actually going on here, and whether the role Nixpkgs may be playing is a problem in its own right
<lukegb> My gut feeling is fetchurl or related though
andi- has joined #nixos-dev
<abathur> ah, hmm, yeah; I guess I can imagine that
<abathur> I've been wondering if something changed in a builder or hook, though that comment says it's pretty global
<abathur> so fetch would make more sense in that light
<abathur> > ping
<{^_^}> "<derivation /nix/store/i26ixr1v32q6njr1mqnfw93q873m93mh-ping-0.6.0.drv>"
<V> ,ping
<abathur> > spongebobify "I wonder why you ignored my issue then :P"
<{^_^}> pong
<{^_^}> "I WonDER wHy yOu IgnOREd mY iSsUe tHen :p"
<lukegb> Ahh, fetchzip?
<lukegb> This is in master but not release-20.09
<V> abathur: because it has a hash
<V> I don't think the regex catches URLs with fragments?
<abathur> V I did the short nix#id fmt first
<V> nix#4295
<abathur> I assumed it was dead, but maybe it doesn't notice first-word
<{^_^}> https://github.com/NixOS/nix/issues/4295 (by fzakaria, 3 days ago, open): error: moving build output '/nix/store/...-source' from the sandbox to the Nix store: Permission denied
<V> nah it's just favouritism
<abathur> or maybe it tracks who mentions it and doesn't give you another?
<abathur> seems doubtful
<V> (or possibly because you posted a lot of links recently)
<abathur> (but I did mention it this morning)
<abathur> nah
<abathur> I've had a sock in it alllll day :D
<abathur> nix#4295
<{^_^}> https://github.com/NixOS/nix/issues/4295 (by fzakaria, 3 days ago, open): error: moving build output '/nix/store/...-source' from the sandbox to the Nix store: Permission denied
<abathur> bog
<abathur> :)
<abathur> maybe it was actually disconnected briefly
<lukegb> you said 4925 instead of 4295
<lukegb> :^)
<abathur> oh
<abathur> yeesh
<abathur> <3 lukegb
<{^_^}> lukegb's karma got increased to 9
supersandro2000 has quit [Read error: Connection reset by peer]
supersandro2000 has joined #nixos-dev
supersandro2000 has quit [Disconnected by services]
supersandro2000 has joined #nixos-dev
<lukegb> abathur: yeah, figured it out
<lukegb> rename requires you to have write permissions on the directory you're renaming, because it updates ".."
<V> oho
<abathur> lulz
<abathur> good errata to know
<abathur> makes sense, but I can see how it's easy to miss
<{^_^}> lukegb's karma now has 2 digits!
<lukegb> how many amusing messages does this bot have
supersandro2000 has quit [Quit: The Lounge - https://thelounge.chat]
supersandro2000 has joined #nixos-dev
alp has joined #nixos-dev
m1cr0man has quit [Quit: G'luck]
m1cr0man has joined #nixos-dev
red[evilred] has joined #nixos-dev
<red[evilred]> So - a philosophical question
<red[evilred]> When there is a package with package, package_10, package_15 etc etc... for different versions
<red[evilred]> at what point does the default package change from being an alias from _10 to say _15?
<red[evilred]> it is down to the package maintainer to do in unstable? ... (and it doesn't propogate to stable)?
<samueldr> maintainer, and I guess, community
<V> in theory? the version should probably be the latest stable. in practise? it's nixpkgs
<samueldr> I don't know if it should be the latest stable
<samueldr> but most situations it's likely the better option
<V> nix-repl> python.version
<V> "2.7.18"
<V> is this the correct result?
<samueldr> nah, should be a throw stating that python 2 has been removed
<V> indeed
<samueldr> python is dead, long live python3
<V> nix-repl> guile.version
<V> "2.2.7"
<V> similarly, 3.0 was released quite some time ago
<samueldr> imo, if it was my opinion only, it would be that "versioned" stuff like that don't get an unversioned attribute name
<samueldr> but not to version everything under the sun
<V> ehh
<V> there's a lot of things to take into account here
<samueldr> maybe something like a "user porcelain" step that callPackage is unaware of to allow nix-shell -p foo # but actually foo_3
<samueldr> things that end up forked like that are always going to break things down the road
<samueldr> because the alias was changed to point to the newer version
<samueldr> if at least internal to Nixpkgs it was never used, that's already a step up
<red[evilred]> The reason I ask is because of julia
<red[evilred]> nix-shell -p julia
<red[evilred]> for a surprise
<samueldr> > julia.meta.description
<{^_^}> "High-level performance-oriented dynamical language for technical computing"
<samueldr> > julia.version
<{^_^}> "1.5.3"
kalbasit has quit [Ping timeout: 256 seconds]
<samueldr> (I don't know julia)
<red[evilred]> interesting
<red[evilred]> how did you get 1.5.3?
<samueldr> > pkgs.version
<{^_^}> attribute 'version' missing, at (string):440:1
<samueldr> > lib.version
<{^_^}> "21.03pre-git"
<samueldr> whatever is fed to the bot
<red[evilred]> that must have been bumped very recently
<samueldr> > stable.julia.version
<{^_^}> "1.0.4"
<red[evilred]> what's ammusing - is that 1.0.4 is marked as broken
<V> > lib.commitIdFromGitRepo <nixpkgs>
<{^_^}> access to path '/var/lib/nixbot/nixpkgs/master' is forbidden in restricted mode
<V> :(((((
<V> > lib.commitIdFromGitRepo path
<{^_^}> access to path '/var/lib/nixbot/nixpkgs/master' is forbidden in restricted mode
<V> alas
<samueldr> it'd be nice if the checkout somehow cheated to give the commit id
<V> well
<samueldr> I don't know how infinisil setup that thing
<V> is this like with the channels? where you have .version or such
<samueldr> if it'd be trivial to just dump git rev-parse HEAD into .version
<samueldr> or something like that
<red[evilred]> this git blame is going to take a while
<red[evilred]> but I'm curious to know how long ago that switched
<samueldr> search through nixpkgs PRs :)
<red[evilred]> 1e4c335a94b2 pkgs/top-level/all-packages.nix (Doron Behar 2020-11-18 15:33:18 +0200 9666) julia = julia_15;
<red[evilred]> found it
<red[evilred]> apparently julia_13 is also marked as broiken on his 20.09 system
<red[evilred]> which means that 20.09 doesn't have a non-broken stable system I guess?
alp has quit [Ping timeout: 272 seconds]
cole-h has quit [Ping timeout: 240 seconds]
alp has joined #nixos-dev
orivej has joined #nixos-dev
saschagrunert has joined #nixos-dev
<stigo> can someone familiar with ZooKeeper have a look at #104889, the Perl stuff looks good to me but would love another set of eyes on the PR
<{^_^}> https://github.com/NixOS/nixpkgs/pull/104889 (by ztzg, 1 week ago, open): zookeeper: 3.4.12 -> 3.6.2 & assorted changes
costrouc has quit [Ping timeout: 264 seconds]
costrouc has joined #nixos-dev
abathur has quit [Ping timeout: 256 seconds]
teto has joined #nixos-dev
sgrunert has joined #nixos-dev
saschagrunert has quit [Ping timeout: 272 seconds]
abathur has joined #nixos-dev
FRidh has joined #nixos-dev
<eyJhb> Would it be insane to include firefoxExtenions in Nixpkgs? https://github.com/NixOS/nixpkgs/issues/105783
<{^_^}> #105783 (by eyJhb, 21 hours ago, open): Firefox extensions discussion
abathur has quit [Ping timeout: 256 seconds]
abathur has joined #nixos-dev
<jtojnar> ryantm: opened https://github.com/jgm/pandoc/pull/6922 to allow us to write proper admonitions in markdown
<{^_^}> jgm/pandoc#6922 (by jtojnar, 36 minutes ago, open): Docbook writer: handle admonitions
<eyJhb> Thanks for the input niksnut :D Was also the feeling I somewhat had. nixpkgs is already huuuge
FRidh has quit [Remote host closed the connection]
FRidh has joined #nixos-dev
thibm has joined #nixos-dev
red[evilred] has quit [Quit: Idle timeout reached: 10800s]
alp has quit [Remote host closed the connection]
alp has joined #nixos-dev
janneke has quit [Remote host closed the connection]
janneke has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
mkaito has joined #nixos-dev
mkaito has joined #nixos-dev
mkaito has quit [Changing host]
<infinisil> V: samueldr: It pulls from master every minute
supersandro2000 has quit [Quit: The Lounge - https://thelounge.chat]
supersandro2000 has joined #nixos-dev
<siraben> How do I synchronize tags from upstream?
<siraben> The last tag I have in my fork of nixpkgs is 18.09-beta
<symphorien[m]> git fetch origin; git push fork --tags
alp has joined #nixos-dev
<siraben> Hm, magit is still showing tag as 18.09-beta
<supersandro2000> git fetch --tags --all
<hexa-> siraben: that's because there haven't been any new release tags on master since then
<hexa-> sadly
<siraben> Oh, what branch should I be tracking?
<hexa-> master? release-20.09?
<hexa-> the thing is, the releases are currently being tagged on the release branch, so we don't even have -alpha tags
<hexa-> which is a bit sad
<siraben> Ah, so I have been fetching the tags correctly I assume
mkaito has joined #nixos-dev
mkaito has quit [Changing host]
mkaito has joined #nixos-dev
<{^_^}> #91724 (by Luis-Hebendanz, 22 weeks ago, merged): Firefox nix addon support
<{^_^}> #105796 (by Luis-Hebendanz, 23 hours ago, open): Fix firefox wrapper
<supersandro2000> you can't umerge
<supersandro2000> you can revert
<supersandro2000> but the one PR is months old and the other a day
<eyJhb> supersandro2000: It was merged 1 day ago, and I know you cannot unmerge, but was meant as a revert
<eyJhb> Because it is breaking peoples Firefox setups
<eyJhb> And it is slowing moving out into the channels atm.
<{^_^}> #105885 (by cmm, 15 minutes ago, open): firefox removed all my add-ons
<eyJhb> Pinging Mic92 :)
<supersandro2000> I'd rather merge the bugfix than reverting things now if we can fix it in a day or two
<Mic92> supersandro2000: makes sense
<supersandro2000> but I do not use Firefox with nix so I can't test things
<eyJhb> It makes sense, but at the same time it should maybe have been reverted before it could actually do some damagae, but atm. it is just poluting :) But yes, it needs to be merged, if it is ready. Also, I can't really test it, as I run a weird setup of FF
<eyJhb> So mine resets whenever anyways
<siraben> Will we be able to specify Firefox flags in configuration.nix/home.nix the future as well?
<siraben> s/the/in the
<supersandro2000> eyJhb: it is on unstable. Please don't rush anything
<andi-> Is there a way to disable the in-browser "apply suggested changes" for the repository? It really messes up the commit history and less git savvy users are getting confused about fetching again and rebasing..
<qyliss> I'd be very surprised
<qyliss> I think committers should just do the rebase in lots of cases
<andi-> Asking people to do things is not working unless you enforce it..
<andi-> I've looked at https://jorisroovers.com/gitlint/ this morning to configure in a way that at least enforces proper commit messages.
<qyliss> interesting
<eyJhb> siraben: you can already do so in home-manager :)
<eyJhb> supersandro2000: I see where that comes from, and I know it is unstable, but a browser is fundamental :)
<siraben> eyJhb: ooh
<eyJhb> siraben: now it is just a matter of using this new PR instead maybe :)
<eyJhb> However, you cannot do pr. profile stuff using that PR. I had a PR for that, but it requires patching https://github.com/NixOS/nixpkgs/pull/94898
<{^_^}> #94898 (by eyJhb, 16 weeks ago, closed): firefox: add firefox-policies w/ patch
<supersandro2000> qyliss: which is also confusing and sometimes takes 60 or 90 seconds to push
alp has quit [Ping timeout: 272 seconds]
__monty__ has joined #nixos-dev
zarel has quit [Quit: ZNC 1.7.5 - https://znc.in]
zarel has joined #nixos-dev
cole-h has joined #nixos-dev
alp has joined #nixos-dev
kalbasit has joined #nixos-dev
thibm has quit [Ping timeout: 256 seconds]
thibm has joined #nixos-dev
mmlb22 has joined #nixos-dev
mmlb22 has quit [Client Quit]
kalbasit_ has joined #nixos-dev
kalbasit has quit [Ping timeout: 256 seconds]
<ryantm> <jtojnar "ryantm: opened https://github.co"> Cool! Though I hope we can eradicate Docbook before we can practically use that.
mmlb22 has joined #nixos-dev
<FRidh> ryantm: there is a desire from some contributors, in varying degrees, to have additional features on top of commonmark
<ryantm> FRidh: Yeah, I think the way we are doing heading anchors is non-standard (not totally sure).
<ryantm> The RFC accounts for allowing additional features.
<FRidh> ryantm: because there is no standard way
<ryantm> They need to be available in multiple implementations
<ryantm> It would be good to start an Issue with a list of non-standard features that we want to use and document which ones are approved to use.
<FRidh> sounds like stuff for an rfc
<ryantm> I think the RFC gives us leeway to use non-standard features as long as we vet they are available in multiple implementations; I'm hoping that is enough of a guideline to move forward without another RFC.
<ryantm> I noticed https://github.com/NixOS/rfcs/blob/4e6802c5ce53e9d43466e6a8eb0bf6ead835dde6/rfcs/0080-nixos-release-schedule.md uses a different version of heading anchors that are more compatible with the way GitHub renders things.
<siraben> ryantm: updated the cross build DocBook -> MD PR
<ryantm> siraben: I saw, thank you. I'll try to review tonight.
<lukegb> someone want to take a look at https://github.com/NixOS/nixpkgs/pull/105845 to unbreak single-user Linux installs using nixpkgs :^)
<{^_^}> #105845 (by lukegb, 13 hours ago, open): fetchzip: get write permission on unpacked directory
<lukegb> there's a corresponding Nix patch that's in 2.3.10 but imo it's probably best to workaround for people currently on 2.3.9, especially since 2.3.9 is current at latest master :o)
* lukegb steps off soapbox
alp has quit [Ping timeout: 256 seconds]
cole-h has quit [Ping timeout: 240 seconds]
rajivr has quit [Quit: Connection closed for inactivity]
thibm has quit [Quit: WeeChat 2.6]
<ekleog> Did anyone ever look at whether stalebot was actually useful, by eg. looking at the ratio between things correctly marked as stale and things that people have to unmark as stale?
<jtojnar> ryantm: that format only seems to define new in-document alias – it does not look like it gets stored in the generated docbook file
<jtojnar> so we cannot use it unless we change the way we generate the manual
ris has joined #nixos-dev
<jtojnar> ryantm: regarding the admonitions, we can just add the patch to nixpkgs untill pandoc is updated
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-dev
<jtojnar> we will want to have admonitions regardless of the final format so it does not make sense to me to convert them to blockquotes
<ryantm> Yeah sounds good. I merged some changesets that converted them to blockquotes because I didn't think it looked too bad, but I can go back and fix those.
alp has joined #nixos-dev
mmlb22 has quit [Quit: The Lounge - https://thelounge.github.io]
mmlb22 has joined #nixos-dev
FRidh has quit [Read error: Connection reset by peer]
<lovesegfault> Anyone familiar with packaging of Qt apps for Nix around?
<lovesegfault> Trying to get clarity on what's best practice around this: https://github.com/NixOS/nixpkgs/pull/105860/files#r536061416
alp has quit [Ping timeout: 272 seconds]
Scriptkiddi has quit [Quit: killed]
ajs124 has quit [Quit: killed]
das_j has quit [Quit: killed]
ajs124 has joined #nixos-dev
Scriptkiddi has joined #nixos-dev
das_j has joined #nixos-dev
alp has joined #nixos-dev
lukegb has quit [Quit: ~~lukegb out~~]
lukegb has joined #nixos-dev
teto has quit [Ping timeout: 264 seconds]
<worldofpeace> lovesegfault: the qt section in the nixpkgs manual shows that u should use the callpackage function
<lovesegfault> :/
<qyliss> isn't the first result what you want?
<lovesegfault> qyliss: yikes, yes, my test search was tricking me :(
teto has joined #nixos-dev
justanotheruser has quit [Ping timeout: 272 seconds]
justanotheruser has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
alp has joined #nixos-dev
sgrunert has quit [Remote host closed the connection]
tilpner_ has joined #nixos-dev
tilpner_ has quit [Client Quit]
<rnhmjoj> can you take a look at PR #104722? it's a fix for a hardware issue and it should also be backported to 20.09
<{^_^}> https://github.com/NixOS/nixpkgs/pull/104722 (by rnhmjoj, 1 week ago, open): nixos/wireless: fix failure with no interfaces
tilpner_ has joined #nixos-dev
tilpner has quit [Ping timeout: 260 seconds]
tilpner_ is now known as tilpner
<abathur> could use an opinion or two on whether the changes in 3 small bash diffs are ~audience-appropriate for the installer; just all 3 outstanding review comments in create-darwin-volume.sh starting at https://github.com/NixOS/nix/pull/4289/files/85cfa6a9708e8c63604127e6373786b44d457e6a#r533014348
MichaelRaskin has joined #nixos-dev
kalbasit_ has quit [Ping timeout: 240 seconds]
zarel has quit [Quit: ZNC 1.7.5 - https://znc.in]
zarel has joined #nixos-dev